Documentation/devtools/maemo5/gdb
(New page: == Description == GDB, the GNU Project debugger, allows you to see what is going on 'inside' another program while it executes -- or what another program was doing at the moment it crashe...) |
|||
| Line 25: | Line 25: | ||
There are several issues you need to be aware when debugging | There are several issues you need to be aware when debugging | ||
| - | (optimized) code on ARM. Please read the [ | + | (optimized) code on ARM. Please read the debugging guide <ref name="dbg-guide">[[Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide|Maemo debugging guide]]</ref>. |
== Links == | == Links == | ||
| Line 33: | Line 33: | ||
[gdb server man page](/development/documentation/man_pages/gdbserver.html) | [gdb server man page](/development/documentation/man_pages/gdbserver.html) | ||
| - | + | http://www.gnu.org/software/gdb/ | |
| - | + | <references/> | |
== See Also == | == See Also == | ||
- | - | ||
Revision as of 07:21, 7 October 2009
Contents |
Description
GDB, the GNU Project debugger, allows you to see what is going on 'inside' another program while it executes -- or what another program was doing at the moment it crashed.
GDB can do four main kinds of things (plus other things in support of these) to help you catch bugs in the act:
- Start your program, specifying anything that might affect its behavior.
- Make your program stop on specified conditions.
- Examine what has happened, when your program has stopped.
- Change things in your program, so you can experiment with correcting the effects of one bug and go on to learn about another.
Packages
source: gdb
binary: gdb
Usage Examples
There are several issues you need to be aware when debugging (optimized) code on ARM. Please read the debugging guide [1].
Links
[gdb man page](/development/documentation/man_pages/gdb.html)
[gdb server man page](/development/documentation/man_pages/gdbserver.html)
http://www.gnu.org/software/gdb/
See Also
-