OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

* snapshots.readme: Clarify when obvious and non-obvious bugs 

should be reported.
This commit is contained in:
Fred Fish 1993-05-24 18:10:14 +00:00
parent 87c942a80c
commit 225501b7d8
2 changed files with 24 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/doc/ChangeLog
View File

@ -1,3 +1,8 @@
Mon May 24 11:09:06 1993 Fred Fish (fnf@cygnus.com)
* snapshots.readme: Clarify when obvious and non-obvious bugs
should be reported.
Mon May 24 09:00:33 1993 Jim Kingdon (kingdon@lioth.cygnus.com)
* stabs.texinfo (Stabs Format): Misc fixes.

20
gdb/doc/snapshots.readme
View File

@ -1,6 +1,6 @@
GDB SNAPSHOT SYSTEM
(general info)
Updated 5/7/93
Updated 5/24/93
WHAT ARE GDB SNAPSHOTS
----------------------
@ -149,6 +149,24 @@ gnu.gdb.bug). Nobody there will have any idea what you are talking about
and it will just cause confusion.
BUG REPORTS
-----------
Send bug reports to gdb-patches@cygnus.com.
Note that since no testing is done on the snapshots, and snapshots may even
be made when gdb is in an inconsistent state, it may not be unusual for an
occasional snapshot to have a very obvious bug, such as failure to compile
on *any* machine. It is likely that such bugs will be fixed by the next
snapshot, so it really isn't necessary to report them unless they persist
for a couple days.
Bugs which are non-obvious, such as failure to compile on only a specific
machine, a new machine dependent bug (particularly one not detected by the
testsuite), missing machine dependent files, etc should be reported when
you discover them, or have a suggested patch to fix them.
FORMAT FOR PATCHES
------------------