On Thu, Jun 23, 2011 at 2:56 AM, Kagamin <span dir="ltr">&lt;spam@here.lot&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


<div>Andrej Mitrovic Wrote:<br>
<br>
&gt; I just ran into some odd stdout corruption issue while doing parallel<br>
&gt; builds, take a look:<br>
&gt;<br>
</div><div>&gt; <a href="http://i.imgur.com/pgC4o.png" target="_blank">http://i.imgur.com/pgC4o.png</a><br>
&gt;<br>
&gt; I&#39;ve tried building again and it was gone, it looks like an appearance<br>
&gt; of a heisenbug. There might be some bug lurking somewhere in<br>
&gt; std.parallelism, but it&#39;s hard to say when I can&#39;t recreate it.<br>
<br>
</div>console output is unbuffered and stdio loves to call putch. Usually this is ok since one doesn&#39;t run multiple applications on the same console simultaneously. And if it does, a program usually makes it in time. It&#39;s strange to see interwined characters as if it can&#39;t write a character in a context switch time frame. May be a bug in console2?<br>



</blockquote></div><br><div>I don&#39;t think console output is unbuffered.  I think it&#39;s line-buffered by default.  Although it does differ and vary; I think on Windows std.stdio.write(&quot;hello\n&quot;) doesn&#39;t flush but on Linux it does.</div>