/[gentoo]/xml/htdocs/doc/en/bugzilla-howto.xml
Gentoo

Diff of /xml/htdocs/doc/en/bugzilla-howto.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.7 Revision 1.8
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.7 2006/09/02 05:26:46 rane Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.8 2006/11/10 22:19:40 nightmorph Exp $ -->
4 4
5<guide link="/doc/en/bugzilla-howto.xml"> 5<guide link="/doc/en/bugzilla-howto.xml">
6<title>Gentoo Bug Reporting Guide</title> 6<title>Gentoo Bug Reporting Guide</title>
7 7
8<author title="Author"> 8<author title="Author">
9 <mail link="chriswhite@gentoo.org">Chris White</mail> 9 <mail link="chriswhite@gentoo.org">Chris White</mail>
10</author> 10</author>
11<author title="Editor"> 11<author title="Editor">
12 <mail link="fox2mike@gentoo.org">Shyam Mani</mail> 12 <mail link="fox2mike@gentoo.org">Shyam Mani</mail>
13</author> 13</author>
14 14
15<abstract> 15<abstract>
16This document shows the proper method of reporting bugs using Bugzilla. 16This document shows the proper method of reporting bugs using Bugzilla.
17</abstract> 17</abstract>
18 18
19<!-- The content of this document is licensed under the CC-BY-SA license --> 19<!-- The content of this document is licensed under the CC-BY-SA license -->
20<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 20<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
21<license/> 21<license/>
22 22
23<version>1.6</version> 23<version>1.7</version>
24<date>2006-09-01</date> 24<date>2006-11-10</date>
25 25
26<chapter> 26<chapter>
27<title>Introduction</title> 27<title>Introduction</title>
28<section> 28<section>
29<title>Preface</title> 29<title>Preface</title>
30<body> 30<body>
31 31
32<p> 32<p>
33One of the factors that delay a bug being fixed is the way it is reported. By 33One of the factors that delay a bug being fixed is the way it is reported. By
34creating this guide, we hope to help improve the communication between 34creating this guide, we hope to help improve the communication between
35developers and users in bug resolution. Getting bugs fixed is an important, if 35developers and users in bug resolution. Getting bugs fixed is an important, if
36not crucial part of the quality assurance for any project and hopefully this 36not crucial part of the quality assurance for any project and hopefully this
37guide will help make that a success. 37guide will help make that a success.
38</p> 38</p>
39 39
298files. This method is the most preferred if you can spare the extra space. 298files. This method is the most preferred if you can spare the extra space.
299Here's how much the file size varies between debug, strip, and -ggdb enabled 299Here's how much the file size varies between debug, strip, and -ggdb enabled
300programs. 300programs.
301</p> 301</p>
302 302
303<pre caption="Filesize differences With -ggdb flag"> 303<pre caption="Filesize differences With -ggdb flag">
304<comment>(debug symbols stripped)</comment> 304<comment>(debug symbols stripped)</comment>
305-rwxr-xr-x 1 chris users 3140 6/28 13:11 bad_code 305-rwxr-xr-x 1 chris users 3140 6/28 13:11 bad_code
306<comment>(debug symbols enabled)</comment> 306<comment>(debug symbols enabled)</comment>
307-rwxr-xr-x 1 chris users 6374 6/28 13:10 bad_code 307-rwxr-xr-x 1 chris users 6374 6/28 13:10 bad_code
308<comment>(-ggdb flag enabled)</comment> 308<comment>(-ggdb flag enabled)</comment>
309-rwxr-xr-x 1 chris users 19552 6/28 13:11 bad_code 309-rwxr-xr-x 1 chris users 19552 6/28 13:11 bad_code
310</pre> 310</pre>
311 311
312<p> 312<p>
313As you can see, -ggdb adds about <e>13178</e> more bytes to the file size over the one 313As you can see, -ggdb adds about <e>13178</e> more bytes to the file size over
314with debugging symbols. However, as shown above, this increase in file size can 314the one with debugging symbols. However, as shown above, this increase in file
315be worth it if presenting debug information to developers. The backtrace can be 315size can be worth it if presenting debug information to developers. The
316saved to a file by copying and pasting from the terminal (if it's a non-x based 316backtrace can be saved to a file by copying and pasting from the terminal (if
317terminal, you can use gpm. To keep this doc simple, I recommend you read up on 317it's a non-x based terminal, you can use gpm. To keep this doc simple, I
318recommend you read up on the <uri link="/doc/en/gpm.xml#doc_chap4">documentation
318the documentation for gpm to see how to copy and paste with it). Now that we're 319for gpm</uri> to see how to copy and paste with it). Now that we're done with
319done with <c>gdb</c>, we can quit. 320<c>gdb</c>, we can quit.
320</p> 321</p>
321 322
322<pre caption="Quitting GDB"> 323<pre caption="Quitting GDB">
323(gdb) <i>quit</i> 324(gdb) <i>quit</i>
324The program is running. Exit anyway? (y or n) <i>y</i> 325The program is running. Exit anyway? (y or n) <i>y</i>
325$ 326$
326</pre> 327</pre>
327 328
328<p> 329<p>
329This ends the walk-through of <c>gdb</c>. Using <c>gdb</c>, we hope that you will 330This ends the walk-through of <c>gdb</c>. Using <c>gdb</c>, we hope that you will
330be able to use it to create better bug reports. However, there are other types 331be able to use it to create better bug reports. However, there are other types
331of errors that can cause a program to fail during run time. One of the other 332of errors that can cause a program to fail during run time. One of the other
332ways is through improper file access. We can find those using a nifty little 333ways is through improper file access. We can find those using a nifty little
333tool called <c>strace</c>. 334tool called <c>strace</c>.
334</p> 335</p>

Legend:
Removed from v.1.7  
changed lines
  Added in v.1.8

  ViewVC Help
Powered by ViewVC 1.1.20