Difference between revisions of "Development/Tutorials/Debugging"

Jump to: navigation, search
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)]]
* 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.
+

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:


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