diff options
Diffstat (limited to 'chapter06/aboutdebug.xml')
| -rw-r--r-- | chapter06/aboutdebug.xml | 25 |
1 files changed, 13 insertions, 12 deletions
diff --git a/chapter06/aboutdebug.xml b/chapter06/aboutdebug.xml index 5bd7a671e..bad3e08fd 100644 --- a/chapter06/aboutdebug.xml +++ b/chapter06/aboutdebug.xml @@ -5,32 +5,33 @@ Most programs and libraries by default are compiled with debugging symbols and optimizing level 2 (gcc options -g and -O2) and are compiled for a specific CPU. On Intel platforms software is compiled for i386 -processors by default. If you don't wish to run software on other -machines other than your own, you might want to change the default +processors by default. If a user doesn't wish to run software on other +machines other than his own, he might want to change the default compiler options so that they will be compiled with a higher -optimization level, no debugging symbols and generate code for your +optimization level, no debugging symbols and generate code for his specific architecture. Let me first explain what debugging symbols are. </para> <para> -A program compiled with debugging symbols means you can run a program or +A program compiled with debugging symbols means a user can run a program or library through a debugger and the debugger's output will be user friendlier. -These debugging symbols also enlarge the program or library significantly. +These debugging symbols also enlarge the program or library significantly. </para> <para> To remove debugging symbols from a binary (must be an a.out or ELF binary) -run <userinput>strip --strip-debug filename</userinput> You can use wild cards -if you need to strip debugging symbols from multiple files (use something like +run <userinput>strip --strip-debug filename</userinput>. A user can use wild + cards +if he needs to strip debugging symbols from multiple files (use something like strip --strip-debug $LFS/usr/bin/*). Another, easier, options is just not to compile programs with debugging symbols. Most people will probably -never use a debugger on software, so by leaving those symbols out you -can save a lot of diskspace. +never use a debugger on software, so by leaving those symbols out +a lot of diskspace can be saved. </para> <para> -Before you wonder if these debugging symbols would make a big difference, +Before someone wonders if these debugging symbols would make a big difference, here are some statistics: </para> @@ -58,8 +59,8 @@ here are some statistics: <para> Sizes may vary depending on which compiler was used and which C library -version was used to link dynamic programs against, but your results will be -similar if you compare programs with and without debugging symbols. After +version was used to link dynamic programs against, but results will be +similar if a user compares programs with and without debugging symbols. After I was done with this chapter and stripped all debugging symbols from all LFS binaries and libraries I regained a little over 102 MB of disk space. Quite the difference. |