From 3f0c882398e626cd92503b1bd964a32e89f818dc Mon Sep 17 00:00:00 2001 From: Manuel Canales Esparcia Date: Tue, 21 Dec 2004 19:38:32 +0000 Subject: Removed the text in chapter 06. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4446 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter06/aboutdebug.xml | 37 +------------------------------------ 1 file changed, 1 insertion(+), 36 deletions(-) (limited to 'chapter06/aboutdebug.xml') diff --git a/chapter06/aboutdebug.xml b/chapter06/aboutdebug.xml index 4939bb704..55435a9d9 100644 --- a/chapter06/aboutdebug.xml +++ b/chapter06/aboutdebug.xml @@ -7,41 +7,6 @@ About debugging symbols -Most programs and libraries are, by default, compiled with debugging -symbols included (with gcc's -g -option). This means that, 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. - -The inclusion of these debugging symbols, however, 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 bash binary -with debugging symbols: 1200 KB - -a bash binary -without debugging symbols: 480 KB - -Glibc and GCC files (/lib -and /usr/lib) -with debugging symbols: 87 MB - -Glibc and GCC files -without debugging symbols: 16 MB - - - -Sizes may vary somewhat, 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. For -your convenience, the next section shows how to strip all debugging symbols -from all programs and libraries. Information on other ways of optimizing your -system can be found in the hint at . +See testing -- cgit v1.2.3-54-g00ecf