On 2012-Sep-04 23:50:35 +0200, Dimitry Andric d...@freebsd.org wrote:
There's a difference between just using '-g', which should never change
the behaviour of the program at runtime, and adding -DDEBUG or similar
flags on the command line, which may or may not enable extra code, or
even cause
Hi,
Recently a service kept crashing on a production box with a SIGSEGV 11.
So I rebuilt with debug symbols to analyse the core file, by adding
WITH_DEBUG=yes into my make.conf (gcc -g).
It got me thinking, is there any reason why it would be a bad idea to
build all my ports with debug
[ please only choose one mailing list for now on, cross posting is discouraged ]
On 4 September 2012 05:26, Jake Smith j...@avenue22.net wrote:
Hi,
It got me thinking, is there any reason why it would be a bad idea to build
all my ports with debug symbols from now on?
Are there any
On 2012-09-04 17:53, Eitan Adler wrote:
On 4 September 2012 05:26, Jake Smith j...@avenue22.net wrote:
...
It got me thinking, is there any reason why it would be a bad idea to build
all my ports with debug symbols from now on?
Are there any performance hits
Yes. Code size grows and the
On Tue, Sep 04, 2012 at 11:50:35PM +0200, Dimitry Andric wrote:
On 2012-09-04 17:53, Eitan Adler wrote:
On 4 September 2012 05:26, Jake Smith j...@avenue22.net wrote:
...
It got me thinking, is there any reason why it would be a bad idea to
build
all my ports with debug symbols from now on?
On 4 September 2012 17:50, Dimitry Andric d...@freebsd.org wrote:
On 2012-09-04 17:53, Eitan Adler wrote:
On 4 September 2012 05:26, Jake Smith j...@avenue22.net wrote:
...
It got me thinking, is there any reason why it would be a bad idea to
build
all my ports with debug symbols from now