Difference between revisions of "Development/Tutorials/Debugging"

Jump to: navigation, search
m (better text. This page needs work to make it useful :))
Line 1: Line 1:
There are several ways to debug an existing program:
+
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:
* you know your program and insert kDebug statements to trace the course of the program
+
* insert kDebug statements to trace the course of the program
* you use [[KDbg]] from our [[tools]]
+
* use [[../Debugging with GDB|gdb (tutorial)]]
 +
* you use [[KDbg]] from our [[../../Tools|tools]]
 
* you use [[add_trace]]
 
* you use [[add_trace]]
 
This program lets you modify your sourcecode so that an information is printed everytime the program enters a function. This is good if you do not know in which function your problem occurs.
 
This program lets you modify your sourcecode so that an information is printed everytime the program enters a function. This is good if you do not know in which function your problem occurs.

Revision as of 17:08, 22 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:

This program lets you modify your sourcecode so that an information is printed everytime the program enters a function. This is good if you do not know in which function your problem occurs.


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal