# SLUG Mailing List Archives

## [SLUG] Re: Debugging information = more cpu/memory usage?

• To: slug@xxxxxxxxxxx
• Subject: [SLUG] Re: Debugging information = more cpu/memory usage?
• From: Angus Lees <gusl@xxxxxxxxxxxxxxx>
• Date: Wed May 23 22:13:02 2001
• User-agent: Mutt/1.2.5i

\begin{Marshall, Joshua}
> I'm wondering whether the debugging information that is compiled into
> most linux executables affects the cpu and memory usage when the
> application is run?
>
> For example, if I strip all the debugging information out of the
> executables, does it simply reduce the disk space it uses or does it
> also reduce the memory usage?

afaik, strip(1) just removes certain sections from the ELF
file. presumably these sections are not loaded into memory unless
required.

on a .so (or .o), it removes symbols from the exported list, which
presumably makes it a little faster to link to (negligible). i don't
think it actually removes the code behind those symbols.

of course, with smaller files, you're more likely to get more frequent
disk cache hits, etc - so there will also be a (negligible) speed up
there.

core dumps on the other hand, have nothing to do with size or run-time
speed. presuming you delete old core files, there is no good reason to
have core dumps disabled.

--
- Gus