Changeset abdeaad6 for chapter06/aboutdebug.xml

Timestamp:

03/23/2001 03:27:23 AM (23 years ago)

Author:

Gerard Beekmans <gerard@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

08463b5b

Parents:

4848808

Message:

Text update

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@360 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter06/aboutdebug.xml (modified) (2 diffs)

chapter06/aboutdebug.xml

@@ -4 +4 @@
 <para>
 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 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 his 
-specific architecture. Let me first explain what debugging symbols
-are.
+symbols (gcc option -g) Let me explain what these debugging symbols
+are and why you may not want them.
 </para>
 
 <para>
 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. 
+library through a debugger and the debugger's output will be user
+friendly. 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>. 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 
-a lot of diskspace can be saved.
-</para>
-
-<para>
-Before someone wonders if these debugging symbols would make a big difference, 
-here are some statistics:
+Before you start wondering whether these debugging symbols really make a 
+big difference, here are some statistics. Use them to draw your own
+conclusion.
 </para>
 
@@ -59 +44 @@
 
 <para>
-Sizes may vary depending on which compiler was used and which C library
+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 a user compares programs with and without debugging symbols. After
+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 and libraries I regained a little over 102 MB of disk space. Quite
-the difference.
+binaries I regained a little over 102 MB of disk space. Quite the difference.
+</para>
+
+<para>
+To remove debugging symbols from a binary (must be an a.out or ELF
+binary) run <userinput>strip --strip-debug filename</userinput>. Wild cards
+can be used to strip debugging symbols from multiple files (use something 
+like <userinput>strip --strip-debug $LFS/usr/bin/*</userinput>).
+Most people will probably never use a debugger on software, so by
+removing those symbols a lot of diskspace can be regained.
 </para>