Re: --enable-debug does not work with gcc
| От | NikhilS |
|---|---|
| Тема | Re: --enable-debug does not work with gcc |
| Дата | |
| Msg-id | d3c4af540702020054u670d31fes6ce4350c97d96d20@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: --enable-debug does not work with gcc (Gavin Sherry <swm@alcove.com.au>) |
| Ответы |
Re: --enable-debug does not work with gcc
|
| Список | 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
--
EnterpriseDB http://www.enterprisedb.com
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@alcove.com.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
В списке pgsql-hackers по дате отправления: