| [6370fa6] | 1 | <sect1 id="ch06-aboutdebug">
|
|---|
| 2 | <title>About debugging symbols</title>
|
|---|
| 3 |
|
|---|
| 4 | <para>
|
|---|
| 5 | Most programs and libraries by default are compiled with debugging
|
|---|
| [abdeaad6] | 6 | symbols (gcc option -g) Let me explain what these debugging symbols
|
|---|
| 7 | are and why you may not want them.
|
|---|
| [6370fa6] | 8 | </para>
|
|---|
| 9 |
|
|---|
| 10 | <para>
|
|---|
| [81a47c0] | 11 | A program compiled with debugging symbols means a user can run a program or
|
|---|
| [abdeaad6] | 12 | library through a debugger and the debugger's output will be user
|
|---|
| 13 | friendly. These debugging symbols also enlarge the program or library
|
|---|
| 14 | significantly.
|
|---|
| [6370fa6] | 15 | </para>
|
|---|
| 16 |
|
|---|
| 17 | <para>
|
|---|
| [abdeaad6] | 18 | Before you start wondering whether these debugging symbols really make a
|
|---|
| 19 | big difference, here are some statistics. Use them to draw your own
|
|---|
| 20 | conclusion.
|
|---|
| [6370fa6] | 21 | </para>
|
|---|
| 22 |
|
|---|
| 23 | <itemizedlist>
|
|---|
| 24 |
|
|---|
| 25 | <listitem><para>
|
|---|
| 26 | A dynamic Bash binary with debugging symbols: 1.2MB
|
|---|
| 27 | </para></listitem>
|
|---|
| 28 |
|
|---|
| 29 | <listitem><para>
|
|---|
| 30 | A dynamic Bash binary without debugging symbols: 478KB
|
|---|
| 31 | </para></listitem>
|
|---|
| 32 |
|
|---|
| 33 | <listitem><para>
|
|---|
| 34 | /lib and /usr/lib (glibc and gcc files) with debugging
|
|---|
| 35 | symbols: 87MB
|
|---|
| 36 | </para></listitem>
|
|---|
| 37 |
|
|---|
| 38 | <listitem><para>
|
|---|
| 39 | /lib and /usr/lib (glibc and gcc files) without
|
|---|
| 40 | debugging symbols: 16MB
|
|---|
| 41 | </para></listitem>
|
|---|
| 42 |
|
|---|
| 43 | </itemizedlist>
|
|---|
| 44 |
|
|---|
| 45 | <para>
|
|---|
| [abdeaad6] | 46 | Sizes vary depending on which compiler was used and which C library
|
|---|
| [81a47c0] | 47 | version was used to link dynamic programs against, but results will be
|
|---|
| [abdeaad6] | 48 | similar if you compare programs with and without debugging symbols. After
|
|---|
| [6370fa6] | 49 | I was done with this chapter and stripped all debugging symbols from all LFS
|
|---|
| [abdeaad6] | 50 | binaries I regained a little over 102 MB of disk space. Quite the difference.
|
|---|
| 51 | </para>
|
|---|
| 52 |
|
|---|
| 53 | <para>
|
|---|
| 54 | To remove debugging symbols from a binary (must be an a.out or ELF
|
|---|
| 55 | binary) run <userinput>strip --strip-debug filename</userinput>. Wild cards
|
|---|
| 56 | can be used to strip debugging symbols from multiple files (use something
|
|---|
| 57 | like <userinput>strip --strip-debug $LFS/usr/bin/*</userinput>).
|
|---|
| 58 | Most people will probably never use a debugger on software, so by
|
|---|
| [4d994af4] | 59 | removing those symbols a lot of disk space can be regained.
|
|---|
| [6370fa6] | 60 | </para>
|
|---|
| 61 |
|
|---|
| [5c453fa] | 62 | <para>
|
|---|
| 63 | You might find additional information in the optimization hint which can
|
|---|
| 64 | be found at <ulink url="http://cvs.linuxfromscratch.org/index.cgi/hints/">
|
|---|
| 65 | http://cvs.linuxfromscratch.org/index.cgi/hints/</ulink>.
|
|---|
| 66 | </para>
|
|---|
| 67 |
|
|---|
| [6370fa6] | 68 | </sect1>
|
|---|
| 69 |
|
|---|
