On Fri, Mar 08, 2002 at 11:01:07AM -0500, Michael G Schwern wrote: > On Fri, Mar 08, 2002 at 03:56:49PM +0000, Nicholas Clark wrote:
> > Hence, is it -DDEBUGGING that's doing the breakage? > > [Or did I get my assumptions wrong?] > > These work: > > -g > -g -DDEBUGGING > > These don't: > > -O > -O -DDEBUGGING Ah. What does -O0 give you? It's gcc. What does -O -g give you? zero. It should turn the optimiser off, hence avoiding any optimiser bugs, but not enable debugging. I believe that enabling debugging causes all automatic variables to be initialised to zero, so leaving them initialised may smoke out the bug's cause] Nicholas Clark
