Development/Tutorials/Debugging/Debugging with GDB - Revision history

AnneW at 12:32, 13 July 2012

2012-07-13T12:32:56Z

2012-01-31T00:05:55Z

Replace information about obsoleted gdb printers from KDESDK by links and instructions to working and maintained printers from KDevelop.

2011-06-27T15:59:14Z

Fix syntax highlighting.

2008-10-03T09:12:01Z

Made a Note for the important information about --nofork

2008-06-20T15:31:24Z

‎Debugging core files with GDB

2008-06-20T13:38:50Z

Added debugging core files section

2008-03-17T21:45:48Z

mention --nofork

2007-11-24T21:49:25Z

Adding Language Navigation Bar

2006-12-29T18:06:53Z

2006-12-22T21:43:55Z

punctuation

@@ Line 1: / Line 1: @@
-{{Template:I18n/Language Navigation Bar|Development/Tutorials/Debugging/Debugging with GDB}}
 This is a short tutorial on debugging KDE applications. Throughout this
 tutorial I will use "kedit" as an example application.

@@ Line 181: / Line 181: @@
 ==Improving your gdb experience for KDE/Qt applications==
-In the SVN path named "kdesdk", you will find the file [http://websvn.kde.org/trunk/KDE/kdesdk/scripts/kde-devel-gdb kdesdk/scripts/kde-devel-gdb].
+Since version 7 GDB supports Python scripting for pretty printers. There are such scripts for basic Qt types (QString, QList, QMap, QHash, QDateTime and many others) in [http://quickgit.kde.org/?p=kdevelop.git&a=tree&f=debuggers/gdb/printers KDevelop git repository]. Download the scripts and add following lines to your ~/.gdbinit to load the scripts automatically as start:
-This file contains a few macros that help looking into some Qt objects (for instance QString).
-See the beginning of the file for instructions on how to use it.
+ python
 If you want to go even further, you can apply those [http://developer.kde.org/documentation/other/gdb-patches patches to the gdb source],

@@ Line 87: / Line 87: @@
   (gdb)
 Important: many applications use "KUniqueApplication" to ensure that only one instance can exist at a given time in a given KDE session. This is the case for kwin, kontact, konsole, plasma, etc. To debug those applications, attach to them while they're running (see next session) or use <code>set args --nofork</code>
 ==Attaching gdb to already running applications==

@@ Line 153: / Line 153: @@
 Debugging process requires much memory. If you have to inspect crash, you can debug core files. It's much faster and requires less memory. First limit the maximum size of core files and run the application:
   ulimit -c 100000
-  kdevelop --nocrashhandler
+  kedit --nocrashhandler
 Don't forget to use '--nocrashhandler' option. Core file would be created if the application crashed, so you can use gdb with created core file:
   gdb kedit ./core-file #in my system it is core.PID
 ==Improving your gdb experience for KDE/Qt applications==

@@ Line 148: / Line 148: @@
       at ../sysdeps/generic/libc-start.c:92
   (gdb)
 ==Improving your gdb experience for KDE/Qt applications==

@@ Line 86: / Line 86: @@
          if (!GUIenabled)
   (gdb)
 ==Attaching gdb to already running applications==

← Older revision		Revision as of 21:49, 24 November 2007
Line 1:		Line 1:
		+	{{Template:I18n/Language Navigation Bar\|Development/Tutorials/Debugging/Debugging with GDB}}
	This is a short tutorial on debugging KDE applications. Throughout this		This is a short tutorial on debugging KDE applications. Throughout this
	tutorial I will use "kedit" as an example application.		tutorial I will use "kedit" as an example application.

@@ Line 1: / Line 1: @@
 This is a short tutorial on debugging KDE applications. Throughout this
-tutorial I will use "kedit" as example application.
+tutorial I will use "kedit" as an example application.
 ==Debugging with GDB==
-The recommended version of gdb to use is version 4.95 or higher, older
+The recommended version of gdb to use is version 4.95 or higher; older
 versions have problems generating proper backtraces.
@@ Line 50: / Line 50: @@
 You can now set breakpoints everywhere. For example lets set a breakpoint
-in the KApplication constructor. Unfortunately gdb is not very good in
+in the KApplication constructor. Unfortunately, gdb is not very good in
 handling C++ names, so it is not really possible to specify the constructor
 directly after the break command. Instead we look up a line of source