Development/Tutorials/Debugging: Difference between revisions

From KDE TechBase
m (better text. This page needs work to make it useful :))
(Replaced content with "{{Moved To Community | Guidelines_and_HOWTOs/Debugging }}")
 
(17 intermediate revisions by 8 users not shown)
Line 1: Line 1:
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:
{{Moved To Community | Guidelines_and_HOWTOs/Debugging }}
* insert kDebug statements to trace the course of the program
* use [[../Debugging with GDB|gdb (tutorial)]]
* you use [[KDbg]] from our [[../../Tools|tools]]
* 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.

Latest revision as of 09:09, 5 August 2016

This page is now on the community wiki.