* README (Reporting Bugs in GDB): Document the bug web page as the
prefered way of submitting bugs. Fix PR gdb/402. * gdb.texinfo (Bug Reporting): Document that the web is the prefered way of submitting bug reports. (Bug Reporting): Delete the s-mail address as the last resort.
This commit is contained in:
Andrew Cagney
parent
aeec20bafb
commit
129188f6b2
|
|
@ -1,3 +1,9 @@
|
|||
2002-04-07 Andrew Cagney <ac131313@redhat.com>
|
||||
|
||||
* README (Reporting Bugs in GDB): Document the bug web page as the
|
||||
prefered way of submitting bugs.
|
||||
Fix PR gdb/402.
|
||||
|
||||
2002-04-06 Andrew Cagney <ac131313@redhat.com>
|
||||
|
||||
* gdbarch.sh (FP_REGNUM, PC_REGNUM, SP_REGNUM): Allow default of
|
||||
|
|
|
|||
37
gdb/README
37
gdb/README
|
|
@ -2,12 +2,16 @@
|
|||
Updated 23 January, 2002 by Andrew Cagney
|
||||
|
||||
This is GDB, the GNU source-level debugger.
|
||||
A summary of new features is in the file `NEWS'.
|
||||
|
||||
See the GDB home page at http://www.gnu.org/software/gdb/ for up to
|
||||
date release information, mailing list links and archives, etc.
|
||||
A summary of new features is in the file `gdb/NEWS'.
|
||||
|
||||
See the file PROBLEMS for late breaking news.
|
||||
The GDB home page at http://www.gnu.org/software/gdb/ for up to date
|
||||
release information, mailing list links and archives, etc.
|
||||
|
||||
The file `gdb/PROBLEMS' contains information on problems identified
|
||||
late in the release cycle. GDB's bug tracking data base at
|
||||
http://www.gnu.org/software/gdb/bugs/ contains a more complete list of
|
||||
bugs.
|
||||
|
||||
|
||||
Unpacking and Installation -- quick overview
|
||||
|
|
@ -480,22 +484,27 @@ not a complete solution. You will need something on the other end
|
|||
that also speaks UDI.
|
||||
|
||||
|
||||
Reporting Bugs
|
||||
===============
|
||||
Reporting Bugs in GDB
|
||||
=====================
|
||||
|
||||
The correct address for reporting bugs found in gdb is
|
||||
"bug-gdb@gnu.org". Please email all bugs, and all requests for help
|
||||
with GDB, to that address. Please include the GDB version number
|
||||
(e.g., gdb-5.1.1), and how you configured it (e.g., "sun4" or "mach386
|
||||
host, i586-intel-synopsys target"). Since GDB now supports so many
|
||||
There are several ways of reporting bugs in GDB. The prefered
|
||||
method is to use the World Wide Web:
|
||||
|
||||
http://www.gnu.org/software/gdb/bugs/
|
||||
|
||||
As an alternative, the bug report can be submitted, via e-mail, to the
|
||||
address "bug-gdb@gnu.org".
|
||||
|
||||
When submitting a bug, please include the GDB version number (e.g.,
|
||||
gdb-5.1.1), and how you configured it (e.g., "sun4" or "mach386 host,
|
||||
i586-intel-synopsys target"). Since GDB now supports so many
|
||||
different configurations, it is important that you be precise about
|
||||
this. If at all possible, you should include the actual banner that
|
||||
GDB prints when it starts up, or failing that, the actual configure
|
||||
command that you used when configuring GDB.
|
||||
|
||||
For more information on how/whether to report bugs, see the GDB
|
||||
Bugs section of the GDB manual (gdb/doc/gdb.texinfo) or the
|
||||
gdb/CONTRIBUTE file.
|
||||
For more information on how/whether to report bugs, see the
|
||||
Reporting Bugs chapter of the GDB manual (gdb/doc/gdb.texinfo).
|
||||
|
||||
|
||||
Graphical interface to GDB -- X Windows, MS Windows
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
2002-04-07 Andrew Cagney <ac131313@redhat.com>
|
||||
|
||||
* gdb.texinfo (Bug Reporting): Document that the web is the
|
||||
prefered way of submitting bug reports.
|
||||
(Bug Reporting): Delete the s-mail address as the last resort.
|
||||
|
||||
2002-04-05 Andrew Cagney <ac131313@redhat.com>
|
||||
|
||||
* gdbint.texinfo (Target Architecture Definition): Delete
|
||||
|
|
|
|||
|
|
@ -13574,12 +13574,11 @@ individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs
|
|||
distribution.
|
||||
@c should add a web page ref...
|
||||
|
||||
In any event, we also recommend that you send bug reports for
|
||||
@value{GDBN} to this addresses:
|
||||
|
||||
@smallexample
|
||||
bug-gdb@@gnu.org
|
||||
@end smallexample
|
||||
In any event, we also recommend that you submit bug reports for
|
||||
@value{GDBN}. The prefered method is to submit them directly using
|
||||
@uref{http://www.gnu.org/software/gdb/bugs/, @value{GDBN}'s Bugs web
|
||||
page}. Alternatively, the @email{bug-gdb@@gnu.org, e-mail gateway} can
|
||||
be used.
|
||||
|
||||
@strong{Do not send bug reports to @samp{info-gdb}, or to
|
||||
@samp{help-gdb}, or to any newsgroups.} Most users of @value{GDBN} do
|
||||
|
|
@ -13595,16 +13594,6 @@ path back to the sender. Thus, if we need to ask for more information,
|
|||
we may be unable to reach you. For this reason, it is better to send
|
||||
bug reports to the mailing list.
|
||||
|
||||
As a last resort, send bug reports on paper to:
|
||||
|
||||
@smallexample
|
||||
@sc{gnu} Debugger Bugs
|
||||
Free Software Foundation Inc.
|
||||
59 Temple Place - Suite 330
|
||||
Boston, MA 02111-1307
|
||||
USA
|
||||
@end smallexample
|
||||
|
||||
The fundamental principle of reporting bugs usefully is this:
|
||||
@strong{report all the facts}. If you are not sure whether to state a
|
||||
fact or leave it out, state it!
|
||||
|
|
|
|||
Loading…
Reference in New Issue