jkt         09/03/05 12:02:04

  Modified:             bugzilla-howto.xml
  Log:
  - we use -ggdb, not -ggdb3
  - specifying -g -ggdb is redundant

Revision  Changes    Path
1.15                 xml/htdocs/doc/en/bugzilla-howto.xml

file : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.15&view=markup
plain: 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.15&content-type=text/plain
diff : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?r1=1.14&r2=1.15

Index: bugzilla-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- bugzilla-howto.xml  26 Jan 2009 07:34:41 -0000      1.14
+++ bugzilla-howto.xml  5 Mar 2009 12:02:04 -0000       1.15
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.14 
2009/01/26 07:34:41 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.15 
2009/03/05 12:02:04 jkt Exp $ -->
 
 <guide link="/doc/en/bugzilla-howto.xml">
 <title>Gentoo Bug Reporting Guide</title>
@@ -20,8 +20,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.12</version>
-<date>2009-01-25</date>
+<version>1.13</version>
+<date>2009-03-05</date>
 
 <chapter>
 <title>Introduction</title>
@@ -125,14 +125,14 @@
 Just for reference, <e>bad_code</e> is the program we'll be debugging with
 <c>gdb</c> later on. As you can see, the program without debugging symbols is
 3140 bytes, while the program with them is 6374 bytes. That's close to double
-the size! Two more things can be done for debugging. The first is adding ggdb3
-to your CFLAGS and CXXFLAGS. This flag adds more debugging information than is
-generally included. We'll see what that means later on. This is how
-<path>/etc/make.conf</path> <e>might</e> look with the newly added flags.
+the size! Two more things can be done for debugging. The first is adding
+<c>ggdb</c> to your CFLAGS and CXXFLAGS. This flag adds more debugging
+information than is generally included. We'll see what that means later on. 
This
+is how <path>/etc/make.conf</path> <e>might</e> look with the newly added 
flags.
 </p>
 
 <pre caption="make.conf settings">
-CFLAGS="-O1 -pipe -g -ggdb"
+CFLAGS="-O1 -pipe -ggdb"
 CXXFLAGS="${CFLAGS}"
 </pre>
 
@@ -285,7 +285,7 @@
 enabled:
 </p>
 
-<pre caption="Program backtrace with -ggdb3">
+<pre caption="Program backtrace with -ggdb">
 (gdb) <i>bt</i>
 #0  0xb7e4bdc0 in strcpy () from /lib/libc.so.6
 #1  0x0804838c in run_it (input=0x0) at bad_code.c:7




Reply via email to