Re: disturbing g++ 971031 results. defer-pop to blame?

[Jeffrey A Law <law@cygnus.com>]

  In message < 19971103000221.16739@dgii.com >you write:
  > > Hmmm, -fdefer-pop is the default; the compiler will arrange for
  > > -fno-defer-pop to be on inside EH regions and such.  Real strange.
  > 
  > Actually, it's only the default if we're optimizing, right?  That's
  > what I'm led to believe from 'gcc -S' output.   That's actually
  > consistent with some more tests that I just ran.
Oh, yes.  You're absolutely right.  Sometimes I forget that you can
build without -O :-)

  > Perhaps we need to make the c++ tests run with varying -O levels
  > as we do for the gcc tests.  After all, what's another few hours
  > during the build? :-)
I've always thought it should be an option.  But never got up the nerve
to sit down and implement it.

Any chance of just discarding symbolic debugging and debugging the exit
path at the assembly level?  Or maybe just find out where exactly it's
core dumping and try work towards a solution from there?

Jeff