Re: patch for configure.in to set cflags for gdb

Sasha_Vasko@osca.state.mo.us
Tue, 24 Apr 2001 08:26:44 -0500




> Right now there's no good way to turn off code optimization using
> configure.  It seems like the '--enable-gdb' option should disable
> "-O2".  I know that if you are actually using gdb you can debug
> optimized code.  I just don't find this sane however.  Therefore, this
> patch.  Use it or drop it.  No matter to me.  It is against cvs co
> afterstep-stable as of Mon Apr 23 23:29:32 EDT 2001


That's how it used to be, and what I've seen was that some code works
differently while unoptimized, and thus some bugs would not show up while
debugging unoptimized code, mostly when it is related to stack/heap
corruption.

-O2 is perfectly safe level and does not do any funky stuff like loop
unrolling
and function inlining, that may interfere with debugging process. So the
desision has been made to keep -O2 on for debugging.

Thanks alot anyway.

> (__) Doug Alcorn <doug@lathi.net> http://www.lathi.net
chat:lathinet@yahoo|aol


Cheers
Sasha


_______________________________________________
The AfterStep Window Manager for X User's Mailing List
http://mail.afterstep.org/mailman/listinfo/as-users