Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<30C9E24891FFD411B68A009027724CB7443355@eg-002-015.eglin.af.mil>
From:	Keen Wayne A Contr AFRL/MNGG <keenwa AT eglin DOT af DOT mil>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT 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/

- Raw text -