Bug Criteria - Debugging with GDB
Description: Debugging with GDB

Next: Bug Reporting, Up: GDB Bugs

### 31.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.