Ignore:
Timestamp:
01/31/2006 08:17:20 PM (18 years ago)
Author:
Manuel Canales Esparcia <manuel@…>
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.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, 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:
92474b45
Parents:
c4dfdaaa
Message:

Started chapter06 indentation.

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter06/aboutdebug.xml

    rc4dfdaaa r50e693d  
    11<?xml version="1.0" encoding="ISO-8859-1"?>
    2 <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
     2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
     3  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
    34  <!ENTITY % general-entities SYSTEM "../general.ent">
    45  %general-entities;
    56]>
     7
    68<sect1 id="ch-system-aboutdebug">
    7 <title>About Debugging Symbols</title>
    8 <?dbhtml filename="aboutdebug.html"?>
     9  <?dbhtml filename="aboutdebug.html"?>
    910
    10 <para>Most programs and libraries are, by default, compiled with
    11 debugging symbols included (with <command>gcc</command>'s
    12 <parameter>-g</parameter> option). This means that when debugging a
    13 program or library that was compiled with debugging information
    14 included, the debugger can provide not only memory addresses, but also
    15 the names of the routines and variables.</para>
     11  <title>About Debugging Symbols</title>
    1612
    17 <para>However, the inclusion of these debugging symbols enlarges a
    18 program or library significantly. The following is an example of the
    19 amount of space these symbols occupy:</para>
    20  
    21 <itemizedlist>
     13  <para>Most programs and libraries are, by default, compiled with
     14  debugging symbols included (with <command>gcc</command>'s
     15  <parameter>-g</parameter> option). This means that when debugging a
     16  program or library that was compiled with debugging information
     17  included, the debugger can provide not only memory addresses, but also
     18  the names of the routines and variables.</para>
    2219
    23 <listitem><para>a bash binary
    24 with debugging symbols: 1200 KB</para></listitem>
     20  <para>However, the inclusion of these debugging symbols enlarges a
     21  program or library significantly. The following is an example of the
     22  amount of space these symbols occupy:</para>
    2523
    26 <listitem><para>a bash binary
    27 without debugging symbols: 480 KB</para></listitem>
     24  <itemizedlist>
     25    <listitem>
     26      <para>A <command>bash</command> binary with debugging symbols:
     27      1200 KB</para>
     28    </listitem>
     29    <listitem>
     30      <para>A <command>bash</command> binary without debugging symbols:
     31      480 KB</para>
     32    </listitem>
     33    <listitem>
     34      <para>Glibc and GCC files (<filename class="directory">/lib</filename>
     35      and <filename class="directory">/usr/lib</filename>) with debugging
     36      symbols: 87 MB</para>
     37    </listitem>
     38    <listitem>
     39      <para>Glibc and GCC files without debugging symbols: 16 MB</para>
     40    </listitem>
     41  </itemizedlist>
    2842
    29 <listitem><para>Glibc and GCC files (<filename class="directory">/lib</filename>
    30 and <filename class="directory">/usr/lib</filename>)
    31 with debugging symbols: 87 MB</para></listitem>
     43  <para>Sizes may vary depending on which compiler and C library were used,
     44  but when comparing programs with and without debugging symbols, the
     45  difference will usually be a factor between two and five.</para>
    3246
    33 <listitem><para>Glibc and GCC files
    34 without debugging symbols: 16 MB</para></listitem>
    35 
    36 </itemizedlist>
    37 
    38 <para>Sizes may vary depending on which compiler and C
    39 library were used, but when comparing programs with and without debugging
    40 symbols, the difference will usually be a factor between two and
    41 five.</para>
    42 
    43 <para>Because most users will never use a debugger on their system
    44 software, a lot of disk space can be regained by removing these
    45 symbols. The next section shows how to strip all debugging symbols
    46 from the programs and libraries. Additional information on system
    47 optimization can be found at <ulink url="&hints-root;optimization.txt"/>.</para>
     47  <para>Because most users will never use a debugger on their system software,
     48  a lot of disk space can be regained by removing these symbols. The next
     49  section shows how to strip all debugging symbols from the programs and
     50  libraries. Additional information on system optimization can be found at
     51  <ulink url="&hints-root;optimization.txt"/>.</para>
    4852
    4953</sect1>
    50 
Note: See TracChangeset for help on using the changeset viewer.