X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: weird problem with printf()
Date: 20 Sep 2004 17:20:50 GMT
Lines: 22
Message-ID: <2r8hriF17s2guU1@uni-berlin.de>
References: <59493f32 DOT 0409200155 DOT 7ad6ec60 AT posting DOT google DOT com> <2r7rjrF17idfoU2 AT uni-berlin DOT de> <59493f32 DOT 0409200908 DOT 11957104 AT posting DOT google DOT com>
X-Trace: news.uni-berlin.de niIAXEqboQgu2fREBsYXwA9Na611WlNLRvITy4Kxaifc7XJKXfPMWt50YA
X-Orig-Path: not-for-mail
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Aniruddha <aniruddha1981 AT yahoo DOT co DOT in> wrote:
> > Almost certainly not.  The problem, whatever it actually may be, is
> > almost certainly in the (presumably large) portions of your program
> > that you didn't show, and it could be almost literally *anything*.  My
> > assumption being that you're somehow invoking undefined, which just
> > happens to kill your stdout stream (redirect it to /dev/null or
> > whatever).

> Is there any easy way to track where I might be invoking UB?.

No.  Mostly because UB can come out being exactly the expected
behaviour.  I.e. you code may still be doing the right things, but for
the wrong reasons.

Some paths to UB are reasonably easy to check using e.g. memory
allocation checking tools like YAMD.  Others are a lot harder.

But see the other response you got, too --- that's definitely
something you should check.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.