m (Debugging moved to Development/Tutorials/Debugging) |
m (better text. This page needs work to make it useful :)) |
||
| Line 1: | Line 1: | ||
| − | There are several ways to | + | 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 |
| − | * 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. | ||
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 TechBase 