Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <30C9E24891FFD411B68A009027724CB7443355@eg-002-015.eglin.af.mil> From: Keen Wayne A Contr AFRL/MNGG To: "'cygwin@cygwin.com'" Subject: Re: Strange behavior of MSVC's printf under cygwin shell? Date: Mon, 25 Mar 2002 17:00:15 -0600 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/