| 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 front end, libraries or
|
|---|
| 71 | tools.
|
|---|
| 72 |
|
|---|
| 73 | bootstrap
|
|---|
| 74 | GCC fails to bootstrap. This should be filed only if a
|
|---|
| 75 | bootstrap failure prevails for an extended period of time
|
|---|
| 76 | (at least one week) on any platform (and possibly
|
|---|
| 77 | not-so-common conditions like a read-only srcdir), or
|
|---|
| 78 | non-mainstream platforms.
|
|---|
| 79 |
|
|---|
| 80 | c++
|
|---|
| 81 | A problem with the C++ compiler front end.
|
|---|
| 82 |
|
|---|
| 83 | c
|
|---|
| 84 | A problem with the C compiler front end.
|
|---|
| 85 |
|
|---|
| 86 | debug
|
|---|
| 87 | A problem with generating debugging information.
|
|---|
| 88 |
|
|---|
| 89 | driver
|
|---|
| 90 | A problem with a compiler driver, namely gcc, g++, g77,
|
|---|
| 91 | gcj or gnat.
|
|---|
| 92 |
|
|---|
| 93 | fortran
|
|---|
| 94 | A problem with the Fortran compiler front end.
|
|---|
| 95 |
|
|---|
| 96 | inline-asm
|
|---|
| 97 | A problem caused by use of inline assembly.
|
|---|
| 98 |
|
|---|
|
|---|
