Development/Tutorials/Debugging: Difference between revisions
< Development | Tutorials
m (better text. This page needs work to make it useful :)) |
m (mention kdevelop) |
||
| Line 2: | Line 2: | ||
* insert kDebug statements to trace the course of the program | * insert kDebug statements to trace the course of the program | ||
* use [[../Debugging with GDB|gdb (tutorial)]] | * use [[../Debugging with GDB|gdb (tutorial)]] | ||
* | * use a graphical frontend like [http://www.kdevelop.org KDevelop] or [http://kdbg.org/ KDbg], see also the [[../../Tools|tools pages]] | ||
Revision as of 11:25, 24 December 2006
In order to understand an application or find bugs it is useful to trace the code paths and get backtraces. There are several ways to do it:
- insert kDebug statements to trace the course of the program
- use gdb (tutorial)
- use a graphical frontend like KDevelop or KDbg, see also the tools pages