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 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.
What is not different, is that both -g and other debugging options will
generally cause compiling and linking to take longer, since these stages
will have to process the additional debug information.
or security risks with this?
no.
You cannot know in general. If debug options enable a different code
path, you might as well get a security problem with it for free. :)
I have seen many debug printf's which could easily be exploited for
buffer overruns, etc.
However, only using '-g' should make no difference, indeed.
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
