On 2/2/07, Gavin Sherry <[EMAIL PROTECTED]> wrote:

On Fri, 2 Feb 2007, NikhilS wrote:

> Hi,
> Indeed it does, apologies for not doing the entire groundwork. But what
> also does is that it adds -O2 by default for gcc even when
--enable-debug is
> specified. gdb is not able to navigate the stack traces properly with
> optimization in place. Especially tracing of static functions becomes
> difficult. Has this issue been faced by anybody else? If so can try out
> patch to avoid using O2 with enable-debug.

Yes, this is known. The thing with gcc is, it only emits some warnings at
-O2. I'm not that this is why we do not set optimisation to 0 but have
long assumed it to be the case. I imagine that it's fairly standard
practice for people doing debugging to CFLAGS=-O0 as an argument to

True, this is how I myself circumvent this problem too. But IMHO,
explicitly passing CFLAGS when we are invoking --enable-debug (which does
add -g, but leaves some optimization flag around which deters debugging)
does not seem correct?


EnterpriseDB               http://www.enterprisedb.com

Reply via email to