Revision 8834,
986 bytes
checked in by ghudson, 28 years ago
(diff) |
This commit was generated by cvs2svn to compensate for changes in r8833,
which included commits to RCS files with non-trunk default branches.
|
Line | |
---|
1 | If you think you may have found a bug in GNU CC, please |
---|
2 | read the Bugs section of the Emacs manual for advice on |
---|
3 | |
---|
4 | (1) how to tell when to report a bug, |
---|
5 | (2) where to send your bug report, and |
---|
6 | (2) how to write a useful bug report and what information |
---|
7 | it needs to have. |
---|
8 | |
---|
9 | There are three ways to read the Bugs section. |
---|
10 | |
---|
11 | (1) In a printed copy of the GCC manual. You can order one from the |
---|
12 | Free Software Foundation; see the file ORDERS. But if you don't have |
---|
13 | a copy on hand and you think you have found a bug, you shouldn't wait |
---|
14 | to get a printed manual; you should read the section right away as |
---|
15 | described below. |
---|
16 | |
---|
17 | (2) With Info. Start Emacs, do C-h i to enter Info, |
---|
18 | then m gcc RET to get to the GCC manual, then m Bugs RET |
---|
19 | to get to the section on bugs. Or use standalone Info in |
---|
20 | a like manner. (Standalone Info is part of the Texinfo distribution.) |
---|
21 | |
---|
22 | (3) By hand. Search for the chapter "Reporting Bugs" in gcc.texi, or |
---|
23 | cat /usr/local/info/gcc* | more "+/^File: emacs, Node: Bugs," |
---|
Note: See
TracBrowser
for help on using the repository browser.