aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDavid Bryant <david@davidcbryant.net>2022-12-20 09:26:41 -0600
committerDavid Bryant <david@davidcbryant.net>2022-12-20 09:26:41 -0600
commita613960c4be169277fa1192f2aa1d4a6c107e796 (patch)
tree5f4e24923ff17128d3210e0cafce2911c096e717
parentd15c80e1b48c272ccd5b4510c2c139bda30896bc (diff)
Removed redundant verbiage. Rewrote a very clumsy sentence.
To speak of a difference (implying subtraction) and a factor (multiplication) as equivalent is confusing at best.
-rw-r--r--chapter08/aboutdebug.xml17
1 files changed, 8 insertions, 9 deletions
diff --git a/chapter08/aboutdebug.xml b/chapter08/aboutdebug.xml
index d646b797e..e9b90d64b 100644
--- a/chapter08/aboutdebug.xml
+++ b/chapter08/aboutdebug.xml
@@ -17,8 +17,8 @@
the debugger can provide not only memory addresses, but also
the names of the routines and variables.</para>
- <para>However, the inclusion of these debugging symbols enlarges a
- program or library significantly. The following is an example of the
+ <para>The inclusion of these debugging symbols enlarges a
+ program or library significantly. Here are two examples of the
amount of space these symbols occupy:</para>
<itemizedlist>
@@ -28,7 +28,7 @@
</listitem>
<listitem>
<para>A <command>bash</command> binary without debugging symbols:
- 480 KB</para>
+ 480 KB (60% smaller)</para>
</listitem>
<listitem>
<para>Glibc and GCC files (<filename class="directory">/lib</filename>
@@ -36,15 +36,14 @@
symbols: 87 MB</para>
</listitem>
<listitem>
- <para>Glibc and GCC files without debugging symbols: 16 MB</para>
+ <para>Glibc and GCC files without debugging symbols: 16 MB (82% smaller)</para>
</listitem>
</itemizedlist>
- <para>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.</para>
-
- <para>Because most users will never use a debugger on their system software,
+ <para>Sizes will vary depending on which compiler and C library were used,
+ but a program that has been stripped of debugging symbols is usually some
+ 50% to 80% smaller than its unstripped counterpart.
+ 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.</para>