GNU Info

(gcc-300.info)Bugs

---

Next: Service Prev: Trouble Up: Top

---

Enter node , (file) or (file)node

Reporting Bugs
**************

   Your bug reports play an essential role in making GCC reliable.

   When you encounter a problem, the first thing to do is to see if it
is already known.  Note: Trouble.  If it isn't known, then you should
report the problem.

   Reporting a bug may help you by bringing a solution to your problem,
or it may not.  (If it does not, look in the service directory; see
Note: Service.)  In any case, the principal function of a bug report
is to help the entire community by making the next version of GCC work
better.  Bug reports are your contribution to the maintenance of GCC.

   Since the maintainers are very overloaded, we cannot respond to every
bug report.  However, if the bug has not been fixed, we are likely to
send you a patch and ask you to tell us whether it works.

   In order for a bug report to serve its purpose, you must include the
information that makes for fixing the bug.

Criteria

Bug Criteria. Have you really found a bug?

Where

Bug Lists. Where to send your bug report.

Reporting

Bug Reporting. How to report a bug effectively.

GNATS

gccbug. You can use a bug reporting tool.

Known

Trouble. Known problems.

Help

Service. Where to ask for help.