From 2b1174bee649fe5f442631a33e2d004bf0317dc7 Mon Sep 17 00:00:00 2001 From: Gerard Beekmans Date: Wed, 29 Aug 2001 19:29:31 +0000 Subject: text updates git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1113 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter06/aboutdebug.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'chapter06/aboutdebug.xml') diff --git a/chapter06/aboutdebug.xml b/chapter06/aboutdebug.xml index 6389ad89c..30b3ea056 100644 --- a/chapter06/aboutdebug.xml +++ b/chapter06/aboutdebug.xml @@ -2,8 +2,7 @@ About debugging symbols Most programs and libraries by default are compiled with debugging -symbols (gcc option -g) Let me explain what these debugging symbols -are and why you may not want them. +symbols (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 @@ -32,10 +31,7 @@ and gcc files) without debugging symbols: 16MB 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. After -I was done with this chapter and stripped all debugging symbols from all LFS -binaries I regained a little over 102 MB of disk space. Quite the -difference. +similar if you compare programs with and without debugging symbols. To remove debugging symbols from a binary (must be an a.out or ELF binary) run strip --strip-debug filename. Wild cards @@ -44,6 +40,10 @@ 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. +For your convenience, chapter 9 includes one simple command to strip +all debugging symbols from all programs and libraries on your +system. + You might find additional information in the optimization hint which can be found at &hint-root;optimization.txt -- cgit v1.2.3-54-g00ecf