Development/Tutorials/Debugging: Difference between revisions
(link Shared Memory Usage in KDE) |
(Link to moved article, for creating good backtraces) |
||
| Line 10: | Line 10: | ||
* [[/Debugging with GDB|Debugging with GDB]] | * [[/Debugging with GDB|Debugging with GDB]] | ||
* [[Development/FAQs/Debugging_FAQ|Debugging FAQ]] | * [[Development/FAQs/Debugging_FAQ|Debugging FAQ]] | ||
* [[/How to create useful crash reports|How to create useful crash reports]] | |||
* For information on debugging tool such as valgrind and [http://kdbg.org/ KDbg], visit the [[../../Tools|tools pages]]. | * For information on debugging tool such as valgrind and [http://kdbg.org/ KDbg], visit the [[../../Tools|tools pages]]. | ||
[[Category:Programming]] | [[Category:Programming]] | ||
Revision as of 21:04, 30 May 2007
Debugging KDE applications can be done on different levels. Most applications "talk" invisibly through debug statements while they are running. Looking at this information mostly gives you enough info to find out what went wrong. For further details, read the dedicated article about error messages.
On a different level we have post-mortem debugging. This is used after an application died, probably because of a programming error. The drkonqi dialog allows you to create a backtrace, and possibly find out where it went wrong.
There are debuggers like gdb which can do a lot more than just find out where it went wrong. You should read the man page of gdb to find out more, and possibly download 'kdbg', 'ddd', or 'inspire' which make gdb a lot simpler to use. Read Debugging with GDB for a detailed tutorial.
Related Pages
- Shared Memory Usage in KDE
- Using error messages (kDebug)
- Debugging with GDB
- Debugging FAQ
- How to create useful crash reports
- For information on debugging tool such as valgrind and KDbg, visit the tools pages.