Date: Tue, 4 Sep 2012 22:37:26 -0400 From: Eitan Adler <lists@eitanadler.com> To: Dimitry Andric <dim@freebsd.org> Cc: Jake Smith <jake@avenue22.net>, freebsd-ports@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Building with WITH_DEBUG (-g) in make.conf Message-ID: <CAF6rxg=dxo-Azx6ssY3xM9hOwudZNW-sWCFTvMC8YJV5wx7csg@mail.gmail.com> In-Reply-To: <504677AB.8040908@FreeBSD.org> References: <53c5133d8fac4f4353eda0add82e2234@viper-webmail.viper.enta.net> <CAF6rxgncRbkdKHniV5qRSxxt2OR35LomeyJObugRkBeAYMBV6A@mail.gmail.com> <504677AB.8040908@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4 September 2012 17:50, Dimitry Andric <dim@freebsd.org> wrote: > On 2012-09-04 17:53, Eitan Adler wrote: >> >> On 4 September 2012 05:26, Jake Smith <jake@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 flags may enable internal >> debugging in the program itself. > > > 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 totally different code paths. My "no" was relating to debug information specifically. Changing the codepath in any way may open the door to new vulnerabilities. There is nothing specific to this being a debug option that makes this an issue. That said, I should have been more precise. :) -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxg=dxo-Azx6ssY3xM9hOwudZNW-sWCFTvMC8YJV5wx7csg>