Re: debuging postgres

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: debuging postgres
Дата
Msg-id
4919.1093365742@sss.pgh.pa.us
Ответ на
Re: debuging postgres (Gaetano Mendola)
Список
Дерево обсуждения
debuging postgres Gaetano Mendola <mendola@bigfoot.com>
Re: debuging postgres Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: debuging postgres Gaetano Mendola <mendola@bigfoot.com>
Re: debuging postgres Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: debuging postgres Tom Lane <tgl@sss.pgh.pa.us>
Re: debuging postgres Gaetano Mendola <mendola@bigfoot.com>
Gaetano Mendola  writes:
> Christopher Kings-Lynne wrote:
>> ./configure --enable-debug

> Is this enough? I'm seeing that with --enable-debug only the
> option -g is passed to the compiler and the option -O2 is
> still there, is it not better compile with -O0 if you are
> going to debug it?

If you want to single-step through the code a lot, then -O0 is good.
But are you really gonna do that so much?  I do most of my tracing
at the level of function calls.

I tend to use -O1 as a compromise setting --- the code isn't totally
scrambled but it doesn't run like a dog either.  (Also, for development
purposes, -O0 is evil because it disables certain useful warnings in
gcc.)
		regards, tom lane

В списке pgsql-hackers по дате отправления
От: Neil Conway
Дата:
От: Tom Lane
Дата:
FAQ