Does adding debugging information make an executable run through its
code paths slower, or will there be no significant difference? How about
its memory footprint...hideously bloated, or only marginally different?
I'm currently rebuilding my system, and debating whether I should strip
the binaries, because I will often have a bug arise and have occasion to
use GDB; I'd also like to be able to step through eg shared libraries
while debugging some code...does this require explicit linking to a
debugging library (like libc_g or something...I forget its exact name)?
I'm not concerned about disk space.
--
Scott