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?
Well, I use the following:
./configure --prefix=blah --enable-debug --enable-cassert
--enable-depend -
Tom Lane wrote:
> Gaetano Mendola <[EMAIL PROTECTED]> 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 wi
Gaetano Mendola <[EMAIL PROTECTED]> 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
Christopher Kings-Lynne wrote:
in order to debug "step by step" the postmaster,
just to understand better the code, is it enough
to compile it after having exported:
CFLAGS='-O0 -g' ?
do you have any hint and/or tips ?
BTW what do you use for this task ?
./configure --enable-debug
Is this enough?
in order to debug "step by step" the postmaster,
just to understand better the code, is it enough
to compile it after having exported:
CFLAGS='-O0 -g' ?
do you have any hint and/or tips ?
BTW what do you use for this task ?
./configure --enable-debug
Chris
---(end of broadca
Hi all,
in order to debug "step by step" the postmaster,
just to understand better the code, is it enough
to compile it after having exported:
CFLAGS='-O0 -g' ?
do you have any hint and/or tips ?
BTW what do you use for this task ?
Regards
Gaetano Mendola
---(end of broadca
