Development/Tutorials/Debugging - Revision history

AnneW at 18:54, 12 July 2012

2012-07-12T18:54:28Z

Tdfischer: add phonon link

2011-03-19T01:39:18Z

add phonon link

Tstaerk: adding debug symbols

2009-07-11T15:55:30Z

adding debug symbols

Dhaumann: add lang navbar

2008-01-13T16:44:42Z

add lang navbar

Aseigo: /* Related Pages */

2008-01-11T04:54:06Z

‎Related Pages

Jstaniek: /* Related Pages */ Debugging on MS Windows

2007-08-28T18:13:56Z

‎Related Pages: Debugging on MS Windows

Bram85: Link to moved article, for creating good backtraces

2007-05-30T21:04:41Z

Link to moved article, for creating good backtraces

Dhaumann: link Shared Memory Usage in KDE

2007-02-25T13:54:03Z

link Shared Memory Usage in KDE

Aseigo: /* Related Pages */

2007-01-13T00:13:00Z

‎Related Pages

Milliams: Categorise

2007-01-05T17:22:30Z

Categorise

← Older revision		Revision as of 18:54, 12 July 2012
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 17: @@
 *[[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]].
 [[Category:Programming]]

@@ Line 10: / Line 10: @@
 *[[Development/Tutorials/Debugging/Shared Memory Usage in KDE|Shared Memory Usage in KDE]]
 *[[Development/Tutorials/Debugging/Using Error Messages|Using error messages (kDebug)]]
 *[[Development/Tutorials/Debugging/Debugging with GDB|Debugging with GDB]]
 *[[Development/Tutorials/Debugging/Debugging IOSlaves|Debugging IOSlaves]]

@@ 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}}
 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 ==
-*[[/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]]
-*[[/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]].
 [[Category:Programming]]

@@ Line 9: / Line 9: @@
 *[[/Using Error Messages|Using error messages (kDebug)]]
 *[[/Debugging with GDB|Debugging with GDB]]
 *[[/Debugging on MS Windows|Debugging on MS Windows]]
 *[[Development/FAQs/Debugging_FAQ|Debugging FAQ]]

@@ Line 10: / Line 10: @@
 * [[/Debugging with GDB|Debugging with GDB]]
 * [[Development/FAQs/Debugging_FAQ|Debugging FAQ]]
 * For information on debugging tool such as valgrind and [http://kdbg.org/ KDbg], visit the [[../../Tools|tools pages]].
 [[Category:Programming]]

← Older revision		Revision as of 17:22, 5 January 2007
Line 12:		Line 12:
	* valgrind		* valgrind
	* [http://www.kdevelop.org KDevelop] or [http://kdbg.org/ KDbg], see also the [[../../Tools\|tools pages]]		* [http://www.kdevelop.org KDevelop] or [http://kdbg.org/ KDbg], see also the [[../../Tools\|tools pages]]
		+
		+	[[Category:Programming]]