Changeset 7100b62


Ignore:
Timestamp:
Feb 21, 2006, 12:47:03 AM (19 years ago)
Author:
Jim Gifford <clfs@…>
Branches:
clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
Children:
c999585
Parents:
9f696aca
Message:

r645@server (orig r643): manuel | 2005-11-07 11:00:55 -0800
Removed an unused file.

Location:
BOOK/final-system
Files:
1 deleted
1 edited

Legend:

Unmodified
Added
Removed
  • BOOK/final-system/common/aboutdebug.xml

    r9f696aca r7100b62  
    99  <?dbhtml filename="aboutdebug.html"?>
    1010
    11   <title os="a">About Debugging Symbols</title>
     11  <title>About Debugging Symbols</title>
    1212
    1313  <para>Most programs and libraries are, by default, compiled with debugging
     
    1717  addresses, but also the names of the routines and variables.</para>
    1818
    19   <para os="b">However, the inclusion of these debugging symbols enlarges a
     19  <para>However, the inclusion of these debugging symbols enlarges a
    2020  program or library significantly. The following is an example of the
    2121  amount of space these symbols occupy:</para>
    2222
    23   <itemizedlist os="c">
     23  <itemizedlist>
    2424    <listitem>
    2525      <para>a bash binary with debugging symbols: 1200 KB</para>
     
    3838  </itemizedlist>
    3939
    40   <para os="d">Sizes may vary depending on which compiler and C library were used,
     40  <para>Sizes may vary depending on which compiler and C library were used,
    4141  but when comparing programs with and without debugging symbols, the
    4242  difference will usually be a factor between two and five.</para>
    4343
    44   <para os="e">Because most users will never use a debugger on their system software,
     44  <para>Because most users will never use a debugger on their system software,
    4545  a lot of disk space can be regained by removing these symbols. The next
    4646  section shows how to strip all debugging symbols from the programs and
Note: See TracChangeset for help on using the changeset viewer.