Difference between revisions of "Development/Tutorials/Debugging"

Jump to: navigation, search
(Related Pages)
(add lang navbar)
Line 1: Line 1:
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 [[/Using Error Messages|error messages]].
+
{{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]].
  
 
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.
 
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|Debugging with GDB]] for a detailed tutorial.
+
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 [[Development/Tutorials/Debugging/Debugging with GDB|Debugging with GDB]] for a detailed tutorial.
  
 
== Related Pages ==
 
== Related Pages ==
*[[/Shared Memory Usage in KDE|Shared Memory Usage in KDE]]
+
*[[Development/Tutorials/Debugging/Shared Memory Usage in KDE|Shared Memory Usage in KDE]]
*[[/Using Error Messages|Using error messages (kDebug)]]
+
*[[Development/Tutorials/Debugging/Using Error Messages|Using error messages (kDebug)]]
*[[/Debugging with GDB|Debugging with GDB]]
+
*[[Development/Tutorials/Debugging/Debugging with GDB|Debugging with GDB]]
*[[/Debugging IOSlaves|Debugging IOSlaves]]
+
*[[Development/Tutorials/Debugging/Debugging IOSlaves|Debugging IOSlaves]]
*[[/Debugging on MS Windows|Debugging on MS Windows]]
+
*[[Development/Tutorials/Debugging/Debugging on MS Windows|Debugging on MS Windows]]
 
*[[Development/FAQs/Debugging_FAQ|Debugging FAQ]]
 
*[[Development/FAQs/Debugging_FAQ|Debugging FAQ]]
*[[/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]].
  
 
[[Category:Programming]]
 
[[Category:Programming]]

Revision as of 17:44, 13 January 2008


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 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


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