Re: Bug#24217: bigloo not stripped
Rob Browning <rlb@cs.utexas.edu> writes:
> A) This is not release critical.
> B) It should be fixed.
> C) Depending on the size of the binary, not stripping it does more
> than just take up disk space, it takes up extra swap and ram when
> running, and potentially increases memory fragmentation and
> decreases cache locality)
This doesn't make sense to me. How does not stripping the binary make
it take up more RAM and swap?
I'm under the impression that when programs are loaded, only the text
and data segments are mmap()ed from the executable (bss is mmap()ed
from /dev/zero); so the debugging information doesn't even get mapped.
If this is true, not only should the debugging information take up no
extra memory or swap, but code pages and unchanged data pages shouldn't
take up any swap (being mapped directly from the file rather than swap
space).
The debugging information is in a seperate section of the ELF
executable, which is ignored by the dynamic loader. In fact, you
could use objcopy even add a section to any ELF program containing
arbitrary data (e.g. a copy of the GPL, icons), which would be ignored
by the dynamic loader (I've actually done this).
Steve
dunham@cps.msu.edu
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: