From fcc027677da55c41dcaea045f5b9ff8b088e6495 Mon Sep 17 00:00:00 2001 From: Bruce Dubbs Date: Sun, 7 Jun 2020 20:16:00 +0000 Subject: Initial commit of alternative cross LFS git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross2@11897 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter06/aboutdebug.xml | 52 ------------------------------------------------ 1 file changed, 52 deletions(-) delete mode 100644 chapter06/aboutdebug.xml (limited to 'chapter06/aboutdebug.xml') diff --git a/chapter06/aboutdebug.xml b/chapter06/aboutdebug.xml deleted file mode 100644 index f49618c83..000000000 --- a/chapter06/aboutdebug.xml +++ /dev/null @@ -1,52 +0,0 @@ - - - %general-entities; -]> - - - - - 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 provide not only memory addresses, but also - the names of the routines and variables. - - However, the inclusion of these debugging symbols enlarges a - program or library significantly. The following is an example of the - amount of space these symbols occupy: - - - - 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 depending on which compiler and C library were used, - but when comparing programs with and without debugging symbols, the - difference will usually be a factor between two and five. - - Because most users will never use a debugger on their system software, - a lot of disk space can be regained by removing these symbols. The next - section shows how to strip all debugging symbols from the programs and - libraries. - - -- cgit v1.2.3-54-g00ecf