From 44c2fd8fabfe36ee9f8464a04e4f2db42d956ab0 Mon Sep 17 00:00:00 2001 From: Timothy Bauscher Date: Sun, 8 Sep 2002 21:54:14 +0000 Subject: Applied Alex\'s grammar patch git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2082 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter06/aboutdebug.xml | 60 ++++++++++++++++++++++++------------------------ 1 file changed, 30 insertions(+), 30 deletions(-) (limited to 'chapter06/aboutdebug.xml') diff --git a/chapter06/aboutdebug.xml b/chapter06/aboutdebug.xml index a4ffefc52..8d03387fe 100644 --- a/chapter06/aboutdebug.xml +++ b/chapter06/aboutdebug.xml @@ -2,49 +2,49 @@ About debugging symbols -Most programs and libraries by default are compiled with debugging -symbols (gcc option -g). +Most programs and libraries are by default compiled with debugging +symbols included (with gcc option -g). -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 -friendly. These debugging symbols also enlarge the program or library -significantly. - -Before you start wondering whether these debugging symbols really make a -big difference, here are some statistics. Use them to draw your own -conclusion. +When debugging a program or library that was compiled with debugging +information included, the debugger can give you not only memory addresses +but also the names of the routines and variables. + +But the inclusion of these debugging symbols enlarges a program or +library significantly. To get an idea of the amount of space these symbols +occupy, have a look at the following: -A dynamic Bash binary -with debugging symbols: 1.2 MB +a bash binary +with debugging symbols: 1200 KB -A dynamic Bash binary -without debugging symbols: 478 KB +a bash binary +without debugging symbols: 480 KB -/lib and /usr/lib (glibc -and gcc files) with debugging symbols: 87 MB +glibc and gcc files (/lib and /usr/lib) +with debugging symbols: 87 MB -/lib and /usr/lib (glibc -and gcc files) without debugging symbols: 16 MB +glibc and gcc files +without debugging symbols: 16 MB -Sizes vary depending on which compiler was used and which C library -version was used to link dynamic programs against, but results will be -similar if you compare programs with and without debugging symbols. +Sizes may vary a little, depending on which compiler was used and +which C library. But when comparing programs with and without debugging +symbols, the difference will generally be a factor between 2 and 5. + +As most people will probably never use a debugger on their system +software, a lot of disk space can be regained by removing these symbols . -To remove debugging symbols from a binary (must be an a.out or ELF -binary) run strip --strip-debug filename. Wildcards -can be used to strip debugging symbols from multiple files (use something -like strip --strip-debug $LFS/usr/bin/*). Most -people will probably never use a debugger on software, so by removing -those symbols a lot of disk space can be regained. +To remove debugging symbols from a binary (which must be an a.out +or ELF binary), run strip --strip-debug filename. +Wildcards can be used to treat multiple files (use something like +strip --strip-debug $LFS/static/bin/*). For your convenience, chapter 9 includes one simple command to strip -all debugging symbols from the programs and libraries on your system. You -might find additional information in the optimization hint which can be -found at . +all debugging symbols from all programs and libraries on your system. +Additional information on optimization you can find in the hint at +. -- cgit v1.2.3-54-g00ecf