Re: Call for port reports

From: Neil Conway <neilc(at)samurai(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Kevin Brown <kevin(at)sysexperts(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Call for port reports
Date: 2003-10-27 09:57:30
Message-ID: 1067248650.459.22.camel@tokyo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 2003-10-25 at 21:29, Bruce Momjian wrote:
> configure --enable-debug will use -g for the compile, and with
> optimization.

I'm just curious: would there be any benefit to using -g3 when
--enable-debug is specified and -g3 is supported by gcc? From the gcc
man page:

-glevel

[...]

Request debugging information and also use level to specify how
much information. The default level is 2.

Level 1 produces minimal information, enough for making backtraces
in parts of the program that you don't plan to debug. This
includes descriptions of functions and external variables, but no
information about local variables and no line numbers.

Level 3 includes extra information, such as all the macro defini-
tions present in the program. Some debuggers support macro expan-
sion when you use -g3.

Note that in order to avoid confusion between DWARF1 debug level 2,
and DWARF2, neither -gdwarf nor -gdwarf-2 accept a concatenated
debug level. Instead use an additional -glevel option to change
the debug level for DWARF1 or DWARF2.

-Neil

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Neil Conway 2003-10-27 10:05:50 Re: Proposed structure for coexisting major versions
Previous Message Gaetano Mendola 2003-10-27 09:26:27 Re: BEGIN vs START TRANSACTION