1 |
jkt 09/03/05 12:02:04 |
2 |
|
3 |
Modified: bugzilla-howto.xml |
4 |
Log: |
5 |
- we use -ggdb, not -ggdb3 |
6 |
- specifying -g -ggdb is redundant |
7 |
|
8 |
Revision Changes Path |
9 |
1.15 xml/htdocs/doc/en/bugzilla-howto.xml |
10 |
|
11 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.15&view=markup |
12 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.15&content-type=text/plain |
13 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?r1=1.14&r2=1.15 |
14 |
|
15 |
Index: bugzilla-howto.xml |
16 |
=================================================================== |
17 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v |
18 |
retrieving revision 1.14 |
19 |
retrieving revision 1.15 |
20 |
diff -u -r1.14 -r1.15 |
21 |
--- bugzilla-howto.xml 26 Jan 2009 07:34:41 -0000 1.14 |
22 |
+++ bugzilla-howto.xml 5 Mar 2009 12:02:04 -0000 1.15 |
23 |
@@ -1,6 +1,6 @@ |
24 |
<?xml version="1.0" encoding="UTF-8"?> |
25 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
26 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.14 2009/01/26 07:34:41 nightmorph Exp $ --> |
27 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.15 2009/03/05 12:02:04 jkt Exp $ --> |
28 |
|
29 |
<guide link="/doc/en/bugzilla-howto.xml"> |
30 |
<title>Gentoo Bug Reporting Guide</title> |
31 |
@@ -20,8 +20,8 @@ |
32 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
33 |
<license/> |
34 |
|
35 |
-<version>1.12</version> |
36 |
-<date>2009-01-25</date> |
37 |
+<version>1.13</version> |
38 |
+<date>2009-03-05</date> |
39 |
|
40 |
<chapter> |
41 |
<title>Introduction</title> |
42 |
@@ -125,14 +125,14 @@ |
43 |
Just for reference, <e>bad_code</e> is the program we'll be debugging with |
44 |
<c>gdb</c> later on. As you can see, the program without debugging symbols is |
45 |
3140 bytes, while the program with them is 6374 bytes. That's close to double |
46 |
-the size! Two more things can be done for debugging. The first is adding ggdb3 |
47 |
-to your CFLAGS and CXXFLAGS. This flag adds more debugging information than is |
48 |
-generally included. We'll see what that means later on. This is how |
49 |
-<path>/etc/make.conf</path> <e>might</e> look with the newly added flags. |
50 |
+the size! Two more things can be done for debugging. The first is adding |
51 |
+<c>ggdb</c> to your CFLAGS and CXXFLAGS. This flag adds more debugging |
52 |
+information than is generally included. We'll see what that means later on. This |
53 |
+is how <path>/etc/make.conf</path> <e>might</e> look with the newly added flags. |
54 |
</p> |
55 |
|
56 |
<pre caption="make.conf settings"> |
57 |
-CFLAGS="-O1 -pipe -g -ggdb" |
58 |
+CFLAGS="-O1 -pipe -ggdb" |
59 |
CXXFLAGS="${CFLAGS}" |
60 |
</pre> |
61 |
|
62 |
@@ -285,7 +285,7 @@ |
63 |
enabled: |
64 |
</p> |
65 |
|
66 |
-<pre caption="Program backtrace with -ggdb3"> |
67 |
+<pre caption="Program backtrace with -ggdb"> |
68 |
(gdb) <i>bt</i> |
69 |
#0 0xb7e4bdc0 in strcpy () from /lib/libc.so.6 |
70 |
#1 0x0804838c in run_it (input=0x0) at bad_code.c:7 |