nightmorph 06/11/10 22:19:40 Modified: bugzilla-howto.xml Log: added link to gpm guide (copy & paste howto), thanks to diox for suggesting on IRC
Revision Changes Path 1.8 xml/htdocs/doc/en/bugzilla-howto.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.8&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.8&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?r1=1.7&r2=1.8 Index: bugzilla-howto.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- bugzilla-howto.xml 2 Sep 2006 05:26:46 -0000 1.7 +++ bugzilla-howto.xml 10 Nov 2006 22:19:40 -0000 1.8 @@ -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.7 2006/09/02 05:26:46 rane Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.8 2006/11/10 22:19:40 nightmorph 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.6</version> -<date>2006-09-01</date> +<version>1.7</version> +<date>2006-11-10</date> <chapter> <title>Introduction</title> @@ -310,13 +310,14 @@ </pre> <p> -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 -terminal, you can use gpm. To keep this doc simple, I recommend you read up on -the documentation for gpm to see how to copy and paste with it). Now that we're -done with <c>gdb</c>, we can quit. +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 terminal, you can use gpm. To keep this doc simple, I +recommend you read up on the <uri link="/doc/en/gpm.xml#doc_chap4">documentation +for gpm</uri> to see how to copy and paste with it). Now that we're done with +<c>gdb</c>, we can quit. </p> <pre caption="Quitting GDB"> -- [email protected] mailing list
