Difference between revisions of "Development/Tutorials/Debugging"

Revision as of 12: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:

@@ Line 2: / Line 2: @@
 * insert kDebug statements to trace the course of the program
 * use [[../Debugging with GDB|gdb (tutorial)]]
-* you use [[KDbg]] from our [[../../Tools|tools]]
+* use a graphical frontend like [http://www.kdevelop.org KDevelop] or [http://kdbg.org/ KDbg], see also the [[../../Tools|tools pages]]
-* 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.