[gentoo-doc-cvs] cvs commit: bugzilla-howto.xml

[vapier]

vapier      05/08/30 02:51:12

  Modified:    xml/htdocs/doc/en bugzilla-howto.xml
  Log:
  tell users to utilize -ggdb -g instead of -ggdb3 since -ggdb3 can cause problems itself and -ggdb/-g is sufficient most of the time

Revision  Changes    Path
1.6       +9 -9      xml/htdocs/doc/en/bugzilla-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.6&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.6&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/bugzilla-howto.xml.diff?r1=1.5&r2=1.6&cvsroot=gentoo

Index: bugzilla-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- bugzilla-howto.xml	22 Jul 2005 23:46:11 -0000	1.5
+++ bugzilla-howto.xml	30 Aug 2005 02:51:12 -0000	1.6
@@ -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.5 2005/07/22 23:46:11 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.6 2005/08/30 02:51:12 vapier 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.4</version>
-<date>2005-07-22</date>
+<version>1.5</version>
+<date>2005-08-29</date>
 
 <chapter>
 <title>Introduction</title>
@@ -132,7 +132,7 @@
 </p>
 
 <pre caption="make.conf settings">
-CFLAGS="-O2 -pipe -ggdb3"
+CFLAGS="-O1 -pipe -g -ggdb"
 CXXFLAGS="${CFLAGS}"
 </pre>
 
@@ -281,7 +281,7 @@
 This backtrace contains a large number of ?? marks. This is because without
 debug symbols, <c>gdb</c> doesn't know how the program was run. Hence, it is
 crucial that debug symbols are <e>not</e> stripped. Now remember a while ago we
-mentioned the -ggdb3 flag. Let's see what the output looks like with the flag
+mentioned the -ggdb flag. Let's see what the output looks like with the flag
 enabled:
 </p>
 
@@ -296,21 +296,21 @@
 Here we see that a lot more information is available for developers. Not only is
 function information displayed, but even the exact line numbers of the source
 files. This method is the most preferred if you can spare the extra space.
-Here's how much the file size varies between debug, strip, and -ggdb3 enabled
+Here's how much the file size varies between debug, strip, and -ggdb enabled
 programs.
 </p>
 
-<pre caption="Filesize differences With -ggdb3 flag">
+<pre caption="Filesize differences With -ggdb flag">
 <comment>(debug symbols stripped)</comment>
 -rwxr-xr-x  1 chris users 3140  6/28 13:11 bad_code
 <comment>(debug symbols enabled)</comment>
 -rwxr-xr-x  1 chris users 6374  6/28 13:10 bad_code
-<comment>(-ggdb3 flag enabled)</comment>
+<comment>(-ggdb flag enabled)</comment>
 -rwxr-xr-x  1 chris users 19552  6/28 13:11 bad_code
 </pre>
 
 <p>
-As you can see, -ggdb3 adds about <e>13178</e> more bytes to the file size over the one
+As you can see, -ggdb adds about <e>13178</e> more bytes to the file size over the one
 with debugging symbols. However, as shown above, this increase in file size can
 be worth it if presenting debug information to developers. The backtrace can be
 saved to a file by copying and pasting from the terminal (if it's a non-x based



-- 
gentoo-doc-cvs@g.o mailing list