Development/Tutorials/Debugging/How to create useful crash reports - Revision history

Jekyll: /* Retrieving a backtrace with GDB */ add more examples of special applicatioins

2013-02-14T15:18:43Z

‎Retrieving a backtrace with GDB: add more examples of special applicatioins

PanchoS: /* Preparing your KDE packages */ add a cross-reference for Ubuntu

2012-11-29T15:43:15Z

‎Preparing your KDE packages: add a cross-reference for Ubuntu

PanchoS: /* Preparing your KDE packages */ + Project Neon

2012-11-29T15:42:21Z

‎Preparing your KDE packages: + Project Neon

PanchoS: /* Preparing your KDE packages */ + Sabayon

2012-11-08T06:47:13Z

‎Preparing your KDE packages: + Sabayon

PanchoS: + Linux Mint

2012-11-08T00:16:27Z

+ Linux Mint

PanchoS: + Mageia

2012-11-07T23:57:39Z

+ Mageia

PanchoS: /* Mandriva */ Link Mandriva wikipage, stylefix

2012-11-07T23:53:47Z

‎Mandriva: Link Mandriva wikipage, stylefix

PanchoS: /* FreeBSD ports */ One more sentence and Linkfix

2012-11-07T23:49:39Z

‎FreeBSD ports: One more sentence and Linkfix

PanchoS: /* Arch */ Link Arch wikipage

2012-11-07T23:36:11Z

‎Arch: Link Arch wikipage

PanchoS: /* Debian */ Link Debian wikipage

2012-11-07T23:23:37Z

‎Debian: Link Debian wikipage

@@ Line 193: / Line 193: @@
 This will run the application like you are used to, and you can work with it like normal (it only consumes far more memory and may feel sluggish). Now it's time to reproduce your crash. When you succeed, the application just closes and you should return to your GDB prompt. Now it's time to run the 'backtrace' command:
-{{note|Some KDE applications (such as JuK and KTorrent) have special code to ensure that there is only one running instance of the application at a time.  For these applications you should type in "run --nofork" at the (gdb) prompt instead of "run" because otherwise gdb will try to debug the wrong process.  If you are unsure as to whether to use --nofork just try it.  If the application says it's an unknown option you can remove --nofork.}}
+{{note|Some KDE applications (such as plasma-desktop, kmix, rekonq, kmail, kontact, amarok, juk and ktorrent) have special code to ensure that there is only one running instance of the application at a time.  For these applications you should type in "run --nofork" at the (gdb) prompt instead of "run" because otherwise gdb will try to debug the wrong process.  If you are unsure as to whether to use --nofork just try it.  If the application says it's an unknown option you can remove --nofork.}}
   (gdb) thread apply all backtrace

@@ Line 95: / Line 95: @@
 Gentoo has its [http://www.gentoo.org/proj/en/qa/backtraces.xml own document] describing how to proceed.
-===Kubuntu/Ubuntu===
+===Kubuntu===
 The Ubuntu family makes things quite easy. Every official KDE module has an additional package in the repository, suffixed with <tt>-dbg</tt>. Always install <tt>kdelibs5-dbg</tt>, because all KDE applications use kdelibs (kdelibs-dbg for KDE 3 applications). Then you should install a -dbg package for the application which crashed. For example if KOrganizer crashed you should install <tt>kdepim-dbg</tt> as well.  If the program is not from an official KDE module and has no -dbg package, you can install the -dbgsym package from the repository listed on this [https://wiki.kubuntu.org/DebuggingProgramCrash Debugging Program Crashes] page.
 *During the Ubuntu development cycle the Apport crash handler is turned on which will report crashes to launchpad.net and do the backtrace for you, if you would rather use the KDE crash handler turn Apport off in /etc/defaults/apport
@@ Line 121: / Line 121: @@
 ===Sabayon===
 Packages are, by default, installed without debugging symbols in Sabayon. Installing them is however very easy: just change the value of the splitdebug variable to <tt>enable</tt> in <tt>/etc/entropy/client.conf</tt>. After this, next time you install a package, you will also get the corresponding debug symbols. For details, see the document [https://wiki.sabayon.org/?title=Debugging_Symbols_-_splitdebug Debugging Symbols - Splitdebug].
 ===Compile from sources===

@@ Line 110: / Line 110: @@
 Note: the <tt>-debug</tt> packages are in separate repositories. For instance, for all packages in <tt>main</tt>, you'll find the debugging package in repository <tt>debug_main</tt>.
 See also [http://wiki.mandriva.com/en/Development/Howto/Software_Crash this document].
 ===openSUSE===

@@ Line 113: / Line 113: @@
 ===openSUSE===
 You should only install the <tt>-debuginfo</tt> packages, for example: <tt>kdepimlibs4-debuginfo</tt>. You can find these packages in [http://en.opensuse.org/KDE/Repositories KDE repositories]. There is also a dedicated [http://en.opensuse.org/openSUSE:Bugreport_application_crashed openSUSE debugging page].
 ===Compile from sources===

@@ Line 99: / Line 99: @@
 *During the Ubuntu development cycle the Apport crash handler is turned on which will report crashes to launchpad.net and do the backtrace for you, if you would rather use the KDE crash handler turn Apport off in /etc/defaults/apport
 *Starting with Lucid Lynx (10.04) Kubuntu will be forwarding all non kubuntu specific bugs upstream and had disabled Apport so that DrKonqui will be the default crash handler.
 ===Mageia===

@@ Line 101: / Line 101: @@
 ===Mandriva===
-Mandriva 2007.0 and up has additional debugging packages for all of KDE (in fact, for all of its packages). Just install the corresponding <tt>-debug</tt> package, like <tt>kdebase-debug</tt> and <tt>kdemultimedia-debug</tt>. You probably want to install <tt>kdelibs-debug</tt> anyways.
+Mandriva 2007.0 and up has additional debugging packages for every single KDE package. Just install the corresponding <tt>-debug</tt> package, like <tt>kdebase-debug</tt> and <tt>kdemultimedia-debug</tt>. You probably want to install <tt>kdelibs-debug</tt> anyways.
-* Note: the <tt>-debug</tt> packages are in separate repositories. For instance, for all packages in <tt>main</tt>, you'll find the debugging package in repository <tt>debug_main</tt>.
+Note: the <tt>-debug</tt> packages are in separate repositories. For instance, for all packages in <tt>main</tt>, you'll find the debugging package in repository <tt>debug_main</tt>.
 ===openSUSE===

@@ Line 90: / Line 90: @@
 ===FreeBSD ports===
-Please refer to the [http://freebsd.kde.org/faq.php#AKDEapplicationcrashedandIwanttofileabugreportathttpbugskdeorgbutthebacktraceintheKDECrashManagerisuselessWhatcanIdo KDE on FreeBSD FAQ].
+You need to recompile the concerned packages with the <tt>WITH_DEBUG</tt>-flag. Please refer to the [http://freebsd.kde.org/faq.php#AKDEapplicationcrashedandIwanttofileabugreportathttpbugskdeorgbutthebacktraceintheKDEcrashmanagerisuselessWhatcanIdo KDE on FreeBSD FAQ].
 ===Gentoo===

@@ Line 71: / Line 71: @@
 ===Arch===
-Arch is currently one of the few distributions that don't offer debug packages with symbols ([https://bugs.archlinux.org/task/10975 Feature Request]). You therefore need to recompile all concerned packages [[Development/Tutorials/Debugging/Debugging_symbols|with debugging symbols]].
+Arch currently doesn't offer debug packages with symbols ([https://bugs.archlinux.org/task/10975 Feature Request]). You therefore need to recompile all concerned packages with debugging symbols. See their informative document [https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces Getting Traces].
 ===Chakra===

@@ Line 81: / Line 81: @@
 ===Debian===
-Debian offers <tt>-dbg</tt> packages to easy create useful backtraces. Just install the corresponding <tt>-dbg</tt> package. e.g. <tt>kdepim-dbg</tt> for KMail crashes. The dependencies of -dbg makes sure to pull in the other right packages (kdelibs-dbg, gdb, and so on).
+Debian offers <tt>-dbg</tt> packages to easy create useful backtraces. Just install the corresponding <tt>-dbg</tt> package. e.g. <tt>kdepim-dbg</tt> for KMail crashes. The dependencies of -dbg makes sure to pull in the other right packages (kdelibs-dbg, gdb, and so on). See also the Debian document on [http://wiki.debian.org/HowToGetABacktrace How to get a Backtrace].
 ===Fedora===