1 |
fox2mike 05/07/07 11:24:54 |
2 |
|
3 |
Modified: xml/htdocs/doc/en/draft bugzilla-howto.xml |
4 |
Log: |
5 |
Few more minor changes. |
6 |
|
7 |
Revision Changes Path |
8 |
1.2 +26 -26 xml/htdocs/doc/en/draft/bugzilla-howto.xml |
9 |
|
10 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
11 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo |
12 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo |
13 |
|
14 |
Index: bugzilla-howto.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v |
17 |
retrieving revision 1.1 |
18 |
retrieving revision 1.2 |
19 |
diff -u -r1.1 -r1.2 |
20 |
--- bugzilla-howto.xml 7 Jul 2005 11:07:05 -0000 1.1 |
21 |
+++ bugzilla-howto.xml 7 Jul 2005 11:24:54 -0000 1.2 |
22 |
@@ -1,6 +1,6 @@ |
23 |
<?xml version="1.0" encoding="UTF-8"?> |
24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v 1.1 2005/07/07 11:07:05 fox2mike Exp $ --> |
26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v 1.2 2005/07/07 11:24:54 fox2mike Exp $ --> |
27 |
|
28 |
<guide link="/doc/en/bugzilla-howto.xml"> |
29 |
<title>Gentoo Bug Reporting Guide</title> |
30 |
@@ -187,7 +187,7 @@ |
31 |
GDB is free software, covered by the GNU General Public License, and you are |
32 |
welcome to change it and/or distribute copies of it under certain conditions. |
33 |
Type "show copying" to see the conditions. |
34 |
-There is absolutely no warranty for GDB.sType "show warranty" for details. |
35 |
+There is absolutely no warranty for GDB. Type "show warranty" for details. |
36 |
This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". |
37 |
</pre> |
38 |
|
39 |
@@ -213,7 +213,8 @@ |
40 |
program, making it hard for developers to find which one is causing the issue. |
41 |
In order to help them out, we do what's called a backtrace. A backtrace runs |
42 |
backwards through all the functions that occurred upon program execution, to the |
43 |
-function at fault. To get a backtrace, at the (gdb) prompt, type in <c>bt</c>. |
44 |
+function at fault. Functions that return (without causing a crash) will not show |
45 |
+up on the backtrace. To get a backtrace, at the (gdb) prompt, type in <c>bt</c>. |
46 |
You will get something like this: |
47 |
</p> |
48 |
|
49 |
@@ -308,11 +309,11 @@ |
50 |
</pre> |
51 |
|
52 |
<p> |
53 |
-This ends the walk-through of gdb. Using gdb, it is my hope that you will be |
54 |
-able to use it to create better bug reports. However, there are other types of |
55 |
-errors that can cause a program to fail during run time. One of the other ways |
56 |
-is through improper file access. We can find those using a nifty little tool |
57 |
-called <c>strace</c>. |
58 |
+This ends the walk-through of <c>gdb</c>. Using <c>gdb</c>, I hope that you will |
59 |
+be able to use it to create better bug reports. However, there are other types |
60 |
+of errors that can cause a program to fail during run time. One of the other |
61 |
+ways is through improper file access. We can find those using a nifty little |
62 |
+tool called <c>strace</c>. |
63 |
</p> |
64 |
|
65 |
</body> |
66 |
@@ -373,10 +374,10 @@ |
67 |
|
68 |
<p> |
69 |
Aha! So There's the problem. Someone moved the configuration directory to |
70 |
-.foobar2 instead of .foobar. We also see the program reading in "bar" as it |
71 |
-should. In this case, we can recommend the ebuild maintainer to put a warning |
72 |
-about it. For now though, we can copy over the config file from .foobar and |
73 |
-modify it to produce the correct results. |
74 |
+<path>.foobar2</path> instead of <path>.foobar</path>. We also see the program |
75 |
+reading in "bar" as it should. In this case, we can recommend the ebuild |
76 |
+maintainer to put a warning about it. For now though, we can copy over the |
77 |
+config file from .foobar and modify it to produce the correct results. |
78 |
</p> |
79 |
|
80 |
</body> |
81 |
@@ -778,7 +779,7 @@ |
82 |
"Meta-distribution", it can run on other os's besides Linux. Examples are |
83 |
Gentoo on MacOS, Gentoo on FreeBSD, etc. For this example, we'll select All, as |
84 |
this can occur on all types of systems. Build Identifier is what is being used |
85 |
-to report the bugs (for logging purposes).sYou can just leave this as is. Let's |
86 |
+to report the bugs (for logging purposes).You can just leave this as is. Let's |
87 |
see what we have so far: |
88 |
</p> |
89 |
|
90 |
@@ -875,13 +876,12 @@ |
91 |
<figure link="/images/docs/bugzie-new-details.png" caption="New Bug Details"/> |
92 |
|
93 |
<p> |
94 |
-Now as you can see, the bug has been assigned to bug-wranglers [at] gentoo |
95 |
-[dot] org. This is the default location for Application component bugs. However, |
96 |
-bug-wranglers (usually) won't fix our bugs, so we'll reassign it to someone that |
97 |
-can (you can let bug-wranglers re-assign it for you as well). For this we use |
98 |
-the package's metadata.xml. You can normally find them in |
99 |
-/usr/portage/category/package/metadata.xml. Here's one I've made up for |
100 |
-foobar2: |
101 |
+Now as you can see, the bug has been assigned to bug-wranglers@g.o. This |
102 |
+is the default location for Application component bugs. However, bug-wranglers |
103 |
+(usually) won't fix our bugs, so we'll reassign it to someone that can (you can |
104 |
+let bug-wranglers re-assign it for you as well). For this we use the package's |
105 |
+metadata.xml. You can normally find them in |
106 |
+/usr/portage/category/package/metadata.xml. Here's one I've made up for foobar2: |
107 |
</p> |
108 |
|
109 |
<pre caption="metadata.xml"> |
110 |
@@ -901,21 +901,21 @@ |
111 |
|
112 |
<p> |
113 |
Notice the maintainer section.T his lists the maintainer of the package, which |
114 |
-in this case is myself, Chris White. The email listed is chriswhite [at] gentoo |
115 |
-[dot] org. We will use this to re-assign the bug to the proper person. To do |
116 |
-this, click the bubble next to Reassign bug to, then fill in the email: |
117 |
+in this case is myself, Chris White. The email listed is chriswhite@g.o. |
118 |
+We will use this to re-assign the bug to the proper person. To do this, click |
119 |
+the bubble next to Reassign bug to, then fill in the email: |
120 |
</p> |
121 |
|
122 |
<note> |
123 |
A package without a metadata.xml file should be re-assigned to |
124 |
-maintainer-needed [at] gentoo [dot] org. |
125 |
+maintainer-needed@g.o. |
126 |
</note> |
127 |
|
128 |
<figure link="/images/docs/bugzie-reassign.png" caption="Bug Reassignment"/> |
129 |
|
130 |
<p> |
131 |
Then hit the Commit button for the changes to take place. The bug has been |
132 |
-reassigned to me. Shortly afterwards, you notice (by email usually) that I've |
133 |
+reassigned to me. Shortly afterward, you notice (by email usually) that I've |
134 |
responded to your bug. I've stated that I'd like to see an strace log to figure |
135 |
out how the program is trying to access your configuration file. You follow the |
136 |
previous instructions on using strace and obtain an strace log. Now you need to |
137 |
@@ -988,7 +988,7 @@ |
138 |
</ul> |
139 |
|
140 |
<p> |
141 |
-Now shortly afterward, I find the error in the strace log.sI resolve the bug |
142 |
+Now shortly afterward, I find the error in the strace log. I resolve the bug |
143 |
as RESOLVED FIXED and say that there was a change in the location of |
144 |
configuration files, and that I will update the ebuild with a warning about it. |
145 |
The bug now becomes resolved, and you are displayed with this: |
146 |
@@ -1038,7 +1038,7 @@ |
147 |
This concludes the howto on working with Bugzilla. I hope you find this useful. |
148 |
If you have any questions, comments, or ideas regarding this document, please |
149 |
send them to me at <mail |
150 |
-link="chriswhite@g.o">chriswhite [at] gentoo [dot] org</mail>. Special |
151 |
+link="chriswhite@g.o">chriswhite@g.o</mail>. Special |
152 |
thanks go to moreon for his notes on -g flags and compile errors, the people at |
153 |
#gentoo-bugs for helping out with bug-wrangling, and Griffon26 for his notes on |
154 |
maintainer-needed. |
155 |
|
156 |
|
157 |
|
158 |
-- |
159 |
gentoo-doc-cvs@g.o mailing list |