
Chapter 28.
Reporting Bugs in gdb
Your bug reports play an essential role in making gdb reliable.
Reporting a bug may help you by bringing a solution to your problem, or it may not. But in any case
the principal function of a bug report is to help the entire community by making the next version of
gdb work better. Bug reports are your contribution to the maintenance of gdb.
In order for a bug report to serve its purpose, you must include the information that enables us to fix
the bug.
28.1. Have you found a bug?
If you are not sure whether you have found a bug, here are some guidelines:
•
If the debugger gets a fatal signal, for any input whatever, that is a gdb bug. Reliable debuggers
never crash.
•
If gdb produces an error message for valid input, that is a bug. (Note that if you’re cross debugging,
the problem may also be somewhere in the connection to the target.)
•
If gdb does not produce an error message for invalid input, that is a bug. However, you should
note that your idea of "invalid input" might be our idea of "an extension" or "support for traditional
practice".
•
If you are an experienced user of debugging tools, your suggestions for improvement of gdb are
welcome in any case.
28.2. How to report bugs
A number of companies and individuals offer support for gnu products. If you obtained gdb from a
support organization, we recommend you contact that organization first.
You can find contact information for many support companies and individuals in the file
etc/SERVICE
in the gnu Emacs distribution.
In any event, we also recommend that you submit bug reports for gdb. The prefered method is to sub-
mit them directly using http://www.gnu.org/software/gdb/bugs/gdb’s Bugs web page. Alternatively,
the e-mail gateway can be used.
Do not send bug reports to
info-gdb
, or to
help-gdb
, or to any newsgroups.
Most users of gdb do
not want to receive bug reports. Those that do have arranged to receive
bug-gdb
.
The mailing list
bug-gdb
has a newsgroup
gnu.gdb.bug
which serves as a repeater. The mailing
list and the newsgroup carry exactly the same messages. Often people think of posting bug reports to
the newsgroup instead of mailing them. This appears to work, but it has one problem which can be
crucial: a newsgroup posting often lacks a mail 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.
The fundamental principle of reporting bugs usefully is this:
report all the facts
. If you are not sure
whether to state a fact or leave it out, state it!
Often people omit facts because they think they know what causes the problem and assume that some
details do not matter. Thus, you might assume that the name of the variable you use in an example
Содержание ENTERPRISE LINUX 3 - SECURITY GUIDE
Страница 1: ...Red Hat Enterprise Linux 3 Debugging with gdb ...
Страница 12: ...2 Chapter 1 Debugging with gdb ...
Страница 28: ...18 Chapter 4 Getting In and Out of gdb ...
Страница 34: ...24 Chapter 5 gdb Commands ...
Страница 44: ...34 Chapter 6 Running Programs Under gdb ...
Страница 68: ...58 Chapter 8 Examining the Stack ...
Страница 98: ...88 Chapter 10 Examining Data ...
Страница 112: ...102 Chapter 12 Tracepoints ...
Страница 118: ...108 Chapter 13 Debugging Programs That Use Overlays ...
Страница 138: ...128 Chapter 14 Using gdb with Different Languages ...
Страница 144: ...134 Chapter 15 Examining the Symbol Table ...
Страница 170: ...160 Chapter 19 Debugging remote programs ...
Страница 198: ...188 Chapter 21 Controlling gdb ...
Страница 204: ...194 Chapter 22 Canned Sequences of Commands ...
Страница 206: ...196 Chapter 23 Command Interpreters ...
Страница 216: ...206 Chapter 25 Using gdb under gnu Emacs ...
Страница 296: ...286 Chapter 27 gdb Annotations ...
Страница 300: ...290 Chapter 28 Reporting Bugs in gdb ...
Страница 322: ...312 Chapter 30 Using History Interactively ...
Страница 362: ...352 Appendix D gdb Remote Serial Protocol ...
Страница 380: ...370 Appendix F GNU GENERAL PUBLIC LICENSE ...
Страница 386: ...376 Appendix G GNU Free Documentation License ...
Страница 410: ......