<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>windows stdout redirect on Alexander Houghton</title>
    <link>https://alexanderhoughton.co.uk/tag/windows-stdout-redirect/</link>
    <description>Recent content in windows stdout redirect on Alexander Houghton</description>
    <image>
      <title>Alexander Houghton</title>
      <url>https://alexanderhoughton.co.uk/images/social-default.png</url>
      <link>https://alexanderhoughton.co.uk/images/social-default.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 17 Dec 2025 20:59:19 +0000</lastBuildDate>
    <atom:link href="https://alexanderhoughton.co.uk/tag/windows-stdout-redirect/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Redirect all stdout/stderr to console</title>
      <link>https://alexanderhoughton.co.uk/blog/redirect-all-stdout-stderr-to-console/</link>
      <pubDate>Fri, 10 Mar 2023 21:38:42 +0000</pubDate>
      <guid>https://alexanderhoughton.co.uk/blog/redirect-all-stdout-stderr-to-console/</guid>
      <description>If your Windows executable is using /SUBSYSTEM:WINDOWS rather than /SUBSYSTEM:CONSOLE, something you will have noticed your output messages to stdout (printf, std::cout etc) will be missing. You can easily solve this however by spawning your own Windows console window and redirecting stdout to your new console. The code below will redirect all stdout &amp;amp; stderr […]</description>
    </item>
  </channel>
</rss>
