Mail Archives: djgpp/2004/09/20/13:30:18
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.
- Raw text -