RE: [HACKERS] --enable-debug

When I initially mentioned this, I had tried to debug, only to find that
there were no symbols.  So I tried the standard autoconf option, which is
--enable-debug, to get some symbols.  I'm not particularly concerned about
--cassert, but --enable-debug is the standard autoconf option, and most
people (developers) are aware of it.  If it's just a synonym for --cassert,
well, I don't really care.  I just want some symbols to debug with.  I
landed up fixing it by setting 
CC=gcc -g -Wall

or something, and recompiling.

MikeA

>> -----Original Message-----
>> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
>> Sent: Wednesday, January 26, 2000 8:04 AM
>> To: Tom Lane
>> Cc: Peter Eisentraut; PostgreSQL Development
>> Subject: Re: [HACKERS] --enable-debug
>> 
>> 
>> > Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> > >> Currently, I believe -Wall is turned on automatically 
>> if your compiler
>> > >> is gcc --- at least it seems to work that way on my 
>> platform (maybe
>> > >> it's in the hpux_gcc template?).  Anyway I get a pretty 
>> good set of -W
>> > >> options without doing anything special.
>> > 
>> > > I remember when we removed every warning gcc -Wall 
>> complained about.
>> > 
>> > Um, did we stop?
>> > 
>> > In my experience, gcc is an excellent detector of 
>> portability problems.
>> > I believe that it is good practice to crank gcc's warning level out
>> > to the max, and to fix everything that it complains about.
>> > 
>> 
>> No, we fixed all the code gcc warned about.  Our code is 100% clean. 
>> The only problems are fork() handling, and patches people 
>> have submitted
>> that were not 100% clean and will be fixed before final.
>> 
>> -- 
>>   Bruce Momjian                        |  http://www.op.net/~candle
>>   pgman@candle.pha.pa.us               |  (610) 853-3000
>>   +  If your life is a hard drive,     |  830 Blythe Avenue
>>   +  Christ can be your backup.        |  Drexel Hill, 
>> Pennsylvania 19026
>> 
>> ************
>>