Skip site navigation (1) Skip section navigation (2)

Re: --enable-debug does not work with gcc

From: NikhilS <nikkhils(at)gmail(dot)com>
To: "Gavin Sherry" <swm(at)alcove(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: --enable-debug does not work with gcc
Date: 2007-02-02 08:54:01
Message-ID: d3c4af540702020054u670d31fes6ce4350c97d96d20@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi,

Indeed it does, apologies for not doing the entire groundwork. But what it
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 this
optimization in place. Especially tracing of static functions becomes
difficult. Has this issue been faced by anybody else? If so can try out a
patch to avoid using O2 with enable-debug.

Regards,
Nikhils

On 2/2/07, Gavin Sherry <swm(at)alcove(dot)com(dot)au> wrote:
>
> On Fri, 2 Feb 2007, NikhilS wrote:
>
> > Hi,
> >
> > configure with --enable-debug does not seem to add "-g" to CFLAGS while
> > compiling with gcc. Guess we will need to change configure.in as below:
>
> Erm... works for me and everyone else... AFAIK.
>
> Thanks,
>
> Gavin
>



-- 
EnterpriseDB               http://www.enterprisedb.com

In response to

Responses

pgsql-hackers by date

Next:From: Jeremy DrakeDate: 2007-02-02 08:54:30
Subject: Re: writing new regexp functions
Previous:From: Kate FDate: 2007-02-02 08:40:20
Subject: Re: Function proposal to find the type of a datum

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group