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