| 1 | <html>
|
|---|
| 2 |
|
|---|
| 3 | <head>
|
|---|
| 4 | <title>Submitting Bug Reports using GNATS</title>
|
|---|
| 5 | </head>
|
|---|
| 6 |
|
|---|
| 7 | <h1>Submitting Bug Reports using GNATS</h1>
|
|---|
| 8 |
|
|---|
| 9 | <body>
|
|---|
| 10 | <h2>gnatsweb and gccbug</h2>
|
|---|
| 11 |
|
|---|
| 12 | <p>GNATS, the GNU bug tracking system, is used to track GCC bug reports.
|
|---|
| 13 | Before submitting a bug report, please read the <a
|
|---|
| 14 | href="bugs.html">general instructions</a>.</p>
|
|---|
| 15 |
|
|---|
| 16 | <p>The preferred way to submit a bug report is by means of the
|
|---|
| 17 | <a href="http://gcc.gnu.org/cgi-bin/gnatsweb.pl?database=gcc&user=guest&password=guest&cmd=login">gnatsweb</a>
|
|---|
| 18 | interface. Make sure you include an e-mail address, so we can inform
|
|---|
| 19 | you when the status of your report changes.</p>
|
|---|
| 20 |
|
|---|
| 21 | <p>Another way is to use the <code>gccbug</code> program that is
|
|---|
| 22 | automatically installed with current versions of GCC, which submits the bug
|
|---|
| 23 | report by e-mail.</p>
|
|---|
| 24 |
|
|---|
| 25 | <p>Both techniques use the same GNATS bug database.</p>
|
|---|
| 26 |
|
|---|
| 27 | <h2>Filling out a report</h2>
|
|---|
| 28 |
|
|---|
| 29 | <p>The bug report form provides a number of fields; you'll need to
|
|---|
| 30 | fill-out most of those (as indicated below) to provide a complete
|
|---|
| 31 | report. The fields have the following purpose:</p>
|
|---|
| 32 |
|
|---|
| 33 | <dl>
|
|---|
| 34 | <dt><strong>Originator</strong></dt>
|
|---|
| 35 | <dd>Your name.</dd>
|
|---|
| 36 |
|
|---|
| 37 | <dt><strong>Organization</strong></dt>
|
|---|
| 38 | <dd>Your organization. You can leave this field blank.</dd>
|
|---|
| 39 |
|
|---|
| 40 | <dt><strong>Confidential</strong></dt>
|
|---|
| 41 | <dd>This field is unused and set to 'no'. All bug reports, including
|
|---|
| 42 | sample code, are publicly accessible.</dd>
|
|---|
| 43 |
|
|---|
| 44 | <dt><strong>Synopsis</strong></dt>
|
|---|
| 45 | <dd>A one-line description of the problem; something like "GCC 2.95
|
|---|
| 46 | does not foo", "objc crashes when doing bar".</dd>
|
|---|
| 47 |
|
|---|
| 48 | <dt><strong>Severity</strong></dt>
|
|---|
| 49 | <dd>Can be one of
|
|---|
| 50 | <dl>
|
|---|
| 51 | <dt>critical</dt>
|
|---|
| 52 | <dd>GCC is completely not operational; no work-around known.</dd>
|
|---|
| 53 | <dt>serious</dt>
|
|---|
| 54 | <dd>GCC is not working properly; a work-around is possible.</dd>
|
|---|
| 55 | <dt>non-critical</dt>
|
|---|
| 56 | <dd>Report indicates minor problem.</dd>
|
|---|
| 57 | </dl>
|
|---|
| 58 | </dd>
|
|---|
| 59 |
|
|---|
| 60 | <dt><strong>Priority</strong></dt>
|
|---|
| 61 | <dd>Can be one of
|
|---|
| 62 | <dl>
|
|---|
| 63 | <dt>high</dt>
|
|---|
| 64 | <dd>A solution is necessary as soon as possible. <em>This is reserved to
|
|---|
| 65 | GCC maintainers.</em></dd>
|
|---|
| 66 | <dt>medium</dt>
|
|---|
| 67 | <dd>The problem should be solved in the next release.</dd>
|
|---|
| 68 | <dt>low</dt>
|
|---|
| 69 | <dd>The problem should be solved in a future release.</dd>
|
|---|
| 70 | </dl>
|
|---|
| 71 | </dd>
|
|---|
| 72 |
|
|---|
| 73 | <dt><strong>Category</strong></dt>
|
|---|
| 74 | <dd>This indicates the GCC subproject which is affected by the problem.
|
|---|
| 75 | Currently, it can be one of
|
|---|
| 76 | <dl>
|
|---|
| 77 | <dt>ada</dt>
|
|---|
| 78 | <dd>A problem with the Ada compiler front end, libraries or tools.</dd>
|
|---|
| 79 | <dt>bootstrap</dt>
|
|---|
| 80 | <dd>GCC fails to bootstrap. This should be filed <em>only</em> if a
|
|---|
| 81 | bootstrap failure prevails for an extended period of time (at least
|
|---|
| 82 | one week) on any platform (and possibly not-so-common conditions like
|
|---|
| 83 | a read-only srcdir), or non-mainstream platforms.</dd>
|
|---|
| 84 | <dt>c++</dt>
|
|---|
| 85 | <dd>A problem with the C++ compiler front end.</dd>
|
|---|
| 86 | <dt>c</dt>
|
|---|
| 87 | <dd>A problem with the C compiler front end.</dd>
|
|---|
| 88 | <dt>debug</dt>
|
|---|
| 89 | <dd>A problem with generating debugging information.</dd>
|
|---|
| 90 | <dt>driver</dt>
|
|---|
| 91 | <dd>A problem with a compiler driver, namely <code>gcc</code>,
|
|---|
| 92 | <code>g++</code>, <code>g77</code>, <code>gcj</code> or
|
|---|
| 93 | <code>gnat</code>.</dd>
|
|---|
| 94 | <dt>fortran</dt>
|
|---|
| 95 | <dd>A problem with the Fortran compiler front end.</dd>
|
|---|
| 96 | <dt>inline-asm</dt>
|
|---|
| 97 | <dd>A problem caused by use of inline assembly.</dd>
|
|---|
| 98 | <dt>java</dt>
|
|---|
| 99 | <dd>A problem with the Java compiler front end.</dd>
|
|---|
| 100 | <dt>libf2c</dt>
|
|---|
| 101 | <dd>A problem in the Fortran runtime library.</dd>
|
|---|
| 102 | <dt>libgcj</dt>
|
|---|
| 103 | <dd>A problem in the Java runtime library.</dd>
|
|---|
| 104 | <dt>libobjc</dt>
|
|---|
| 105 | <dd>A problem in the Objective C runtime library.</dd>
|
|---|
| 106 | <dt>libstdc++</dt>
|
|---|
| 107 | <dd>A problem in the Standard C++ runtime library.</dd>
|
|---|
| 108 | <dt>middle-end</dt>
|
|---|
| 109 | <dd>A problem in the internal compiler passes.</dd>
|
|---|
| 110 | <dt>objc</dt>
|
|---|
| 111 | <dd>A problem with the Objective C compiler.</dd>
|
|---|
| 112 | <dt>optimization</dt>
|
|---|
| 113 | <dd>A problem only occurring under optimization.</dd>
|
|---|
| 114 | <dt>preprocessor</dt>
|
|---|
| 115 | <dd>A problem with the C preprocessor.</dd>
|
|---|
| 116 | <dt>target</dt>
|
|---|
| 117 | <dd>The problem depends on the specific target architecture.</dd>
|
|---|
| 118 | <dt>web</dt>
|
|---|
| 119 | <dd>There is an error or omission on the Web pages.</dd>
|
|---|
| 120 | <dt>other</dt>
|
|---|
| 121 | <dd>The problem is in none of these categories.</dd>
|
|---|
| 122 | </dl>
|
|---|
| 123 | </dd>
|
|---|
| 124 |
|
|---|
| 125 | <dt><strong>Class</strong></dt>
|
|---|
| 126 | <dd>A classification of the problem; one of
|
|---|
| 127 | <dl>
|
|---|
| 128 | <dt>doc-bug</dt>
|
|---|
| 129 | <dd>The documentation is incorrect.</dd>
|
|---|
| 130 | <dt>accepts-illegal</dt>
|
|---|
| 131 | <dd>GCC fails to reject erroneous code.</dd>
|
|---|
| 132 | <dt>rejects-legal</dt>
|
|---|
| 133 | <dd>GCC gives an error message for correct code.</dd>
|
|---|
| 134 | <dt>wrong-code</dt>
|
|---|
| 135 | <dd>The machine code generated by GCC is incorrect.</dd>
|
|---|
| 136 | <dt>ice-on-legal-code</dt>
|
|---|
| 137 | <dd>GCC gives an Internal Compiler Error (ICE) for correct code.</dd>
|
|---|
| 138 | <dt>ice-on-illegal-code</dt>
|
|---|
| 139 | <dd>GCC gives an ICE instead of reporting an error.</dd>
|
|---|
| 140 | <dt>pessimizes-code</dt>
|
|---|
| 141 | <dd>GCC misses an important optimization opportunity.</dd>
|
|---|
| 142 | <dt>sw-bug</dt>
|
|---|
| 143 | <dd>Software bug of some other class than above.</dd>
|
|---|
| 144 | <dt>change-request</dt>
|
|---|
| 145 | <dd>A feature in GCC is missing.</dd>
|
|---|
| 146 | <dt>support</dt>
|
|---|
| 147 | <dd>I need help with GCC.</dd>
|
|---|
| 148 | </dl>
|
|---|
| 149 | </dd>
|
|---|
| 150 |
|
|---|
| 151 | <dt><strong>Release</strong></dt>
|
|---|
| 152 | <dd>GCC version, as obtained from 'gcc -v' (one line).</dd>
|
|---|
| 153 |
|
|---|
| 154 | <dt><strong>Environment</strong></dt>
|
|---|
| 155 | <dd>Information about your operating system version, hardware architecture,
|
|---|
| 156 | and environment settings that affect GCC.</dd>
|
|---|
| 157 |
|
|---|
| 158 | <dt><strong>Description</strong></dt>
|
|---|
| 159 | <dd>Precise description of the problem. You should put the error messages
|
|---|
| 160 | printed by GCC here; source code should go into the next section.</dd>
|
|---|
| 161 |
|
|---|
| 162 | <dt><strong>How-To-Repeat</strong></dt>
|
|---|
| 163 |
|
|---|
| 164 | <dd>Please put the complete source code to reproduce the problem here.
|
|---|
| 165 | The gccbug script currently does not support file
|
|---|
| 166 | attachments. Instead, if you have multiple files, include them
|
|---|
| 167 | uuencoded (compressing them before if they are large). If you use
|
|---|
| 168 | gnatsweb, you can use the file attachments button instead.</dd>
|
|---|
| 169 |
|
|---|
| 170 | <dt><strong>Fix</strong></dt>
|
|---|
| 171 | <dd>How to correct or work around the problem, if known (multiple lines).</dd>
|
|---|
| 172 |
|
|---|
| 173 | </dl>
|
|---|
| 174 |
|
|---|
| 175 | </body>
|
|---|
| 176 | </html>
|
|---|
