Difference between revisions of "Development/Tutorials/Debugging"

Jump to: navigation, search
(adding debug symbols)
 
(One intermediate revision by one user not shown)
Line 1: Line 1:
{{Template:I18n/Language_Navigation_Bar|Development/Tutorials/Debugging}}
 
  
 
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 [[Development/Tutorials/Debugging/Using Error Messages|error messages]].
 
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 [[Development/Tutorials/Debugging/Using Error Messages|error messages]].
Line 17: Line 16:
 
*[[Development/Tutorials/Debugging/How to create useful crash reports|How to create useful crash reports]]
 
*[[Development/Tutorials/Debugging/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]].
 +
*[[Development/Tutorials/Debugging/Phonon|Debugging Phonon]]
  
 
[[Category:Programming]]
 
[[Category:Programming]]

Latest revision as of 19:54, 12 July 2012

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.

[edit] Related Pages


This page was last modified on 12 July 2012, at 19:54. This page has been accessed 21,383 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal