I have frequently seen unpredictable behavior of C prints in terms of their timing. (I'm an old guy and I still debug with prints from time to time). The only way I got predictable results was to do a buffer flush immediately after the print. In my case, if I didn't do that, and the program crashed, sometimes I would never see my diagnostic prints.
I have seen this on the SGI and the PC, but I can't swear that the PC was using VC++, it may have been Borland, or Cygwin or... Wayne Keen -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
