DebuggingProgramCrash

Differences between revisions 53 and 56 (spanning 3 versions)
Revision 53 as of 2008-08-02 23:07:21
Size: 4800
Editor: pool-71-103-192-17
Comment: Added reference and link to Bugs/ApportRetraces page.
Revision 56 as of 2008-11-04 08:52:31
Size: 4804
Editor: 59
Comment: Removed Feisty references and added Intrepid references
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[Include(Debugging/Header)]]
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]||
<<Include(Debugging/Header)>>
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||
Line 6: Line 6:
== Feisty Fawn 7.04, Gutsy Gibbon 7.10 and Hardy Heron 8.04 == == Gutsy Gibbon 7.10 , Hardy Heron 8.04 and Intrepid Ibex 8.10 ==
Line 8: Line 8:
Use this section only if you are using Ubuntu '''Feisty 7.04''', '''Gutsy 7.10''' or '''Hardy 8.04'''. See the following section if you are using a prior version. Use this section only if you are using Ubuntu '''Gutsy 7.10''' , '''Hardy 8.04''' or '''Intrepid Ibex'''. See the following section if you are using a prior version.
Line 11: Line 11:
 {{{deb http://ddebs.ubuntu.com hardy main universe
deb http://ddebs.ubuntu.com hardy-updates main universe
deb http://ddebs.ubuntu.com hardy-proposed main universe
deb http://ddebs.ubuntu.com hardy-security main universe
 {{{
deb http://ddebs.ubuntu.com intrepid main universe
deb http://ddebs.ubuntu.com intrepid-updates main universe
deb http://ddebs.ubuntu.com intrepid-proposed main universe
deb http://ddebs.ubuntu.com intrepid-security main universe
Line 46: Line 47:
 a. Now you make a ["Backtrace"].
 a. You can also run ["Valgrind"], if the program crashes with a "Segmentation fault" or "Bus error".
 a. Optionally, you may be asked to produce an ["Strace"].
 a. Now you make a [[Backtrace]].
 a. You can also run [[Valgrind]], if the program crashes with a "Segmentation fault" or "Bus error".
 a. Optionally, you may be asked to produce an [[Strace]].
Line 57: Line 58:
Use this section if you are using an Ubuntu version prior to Feisty 7.04. Use this section if you are using an Ubuntu version prior to Gusty 7.10.
Line 105: Line 106:
Say that you're running `feisty` and the crash happened on `edgy`: Say that you're running `Gutsy` and the crash happened on `fiesty`:
Line 107: Line 108:
 0. This will create a minimal `edgy` system. {{{  0. This will create a minimal `fiesty` system. {{{
Line 110: Line 111:
 0. Now you change into this minimal `edgy` system. {{{  0. Now you change into this minimal `fiesty` system. {{{
Line 117: Line 118:
For more information on dealing with bug reports ["Apport"] see ["Bugs/ApportRetraces"]. For more information on dealing with bug reports [[Apport]] see [[Bugs/ApportRetraces]].

Debugging Central

This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages.

This document describes how to install debug packages on Ubuntu, which will aid in providing information for bugs.

Gutsy Gibbon 7.10 , Hardy Heron 8.04 and Intrepid Ibex 8.10

Use this section only if you are using Ubuntu Gutsy 7.10 , Hardy 8.04 or Intrepid Ibex. See the following section if you are using a prior version.

1. Add the following lines to /etc/apt/sources.list: (of course, replace hardy with feisty if you're using 7.04 or gutsy for 7.10)

  • deb http://ddebs.ubuntu.com intrepid main universe
    deb http://ddebs.ubuntu.com intrepid-updates main universe
    deb http://ddebs.ubuntu.com intrepid-proposed main universe
    deb http://ddebs.ubuntu.com intrepid-security main universe

You may also add these lines using the Synaptic Package Manager:

a. Choose Synaptic via the System > Administration menu.

b. Choose Software Sources via the Settings menu, and click on the Third-Party Software tab.

c. Click the Add button and enter each deb ... line as above one by one and click the Add Source button (you will have to add these lines one at a time).

d. Click the Reload button once you are done adding all the deb lines.

2. Then run

  • sudo apt-get update

to update your package list.

3. The debug symbol packages have the '-dbgsym' suffix attached, so to install the debug symbols for the package 'yelp', you run:

  • dpkg -l yelp

Note the version number installed, e.g. 2.22.1-0ubuntu2.8.04.1, then run:

  • sudo apt-get install yelp-dbgsym=2.22.1-0ubuntu2.8.04.1

Alternatively, main Ubuntu repositories could contain '-dbg' debug symbol packages. Those are equivalent to '-dbgsym'. You could use the one you want, but not both.

  1. Now you make a Backtrace.

  2. You can also run Valgrind, if the program crashes with a "Segmentation fault" or "Bus error".

  3. Optionally, you may be asked to produce an Strace.

  4. You can also provide this file : ~/.xsession-errors

References

Prior Ubuntu versions

Use this section if you are using an Ubuntu version prior to Gusty 7.10.

  1. Check if the package has a debugging version available. In general, debugging packages will be named with a -dbg suffix

  2. If not, you can generally* build one this way:

Something to keep in mind: if you would like to create a build you're going to need to have the relevant deb-src lines in your /etc/apt/sources.list

  1. Install the development scripts:
    sudo apt-get install devscripts fakeroot
  2. Find out to which package your program belongs to:
    dpkg --search <program> 
  3. Install the build-time dependencies for the package:
    sudo apt-get build-dep <package>
  4. Build .debs for debugging:
    export DEB_BUILD_OPTIONS="debug nostrip noopt"
    fakeroot apt-get source -b <package>
  5. Install the needed .debs (they will be in the current working directory if the build succeeded):
    sudo debi <package>*.changes

* Most packages support the build of debugging version in this way. If this process doesn't work for a package, please open a bug against it.

The Xorg server

The X server will by default trap its own crashes and dump a stack trace in /var/log/Xorg.0.log. However, this stack trace is modified by the signal handler itself. To get a "normal" crash, which will trigger a core dump (and apport reporting), add this to your /etc/X11/xorg.conf:

Section "ServerFlags"
        Option "NoTrapSignals" "true"
EndSection

Please see DebuggingXorg for how to debug Xorg server crashes.

Info for the BugSquad

If you're trying to apport-retrace a crash report from a bug that didn't happen on the same Ubuntu release as the one you're running, do the following:

Say that you're running Gutsy and the crash happened on fiesty:

  1. This will create a minimal fiesty system.

    sudo mkdir -p /chroots/edgy
    sudo debootstrap edgy /chroots/edgy/
  2. Now you change into this minimal fiesty system.

    sudo chroot /chroot/edgy
  3. edit /etc/apt/sources/list and all the repositories you need, especially Martin's ddeb repository.

  4. apt-get update; apt-get install gdb apport
  5. use apport-retrace as you're used to.

For more information on dealing with bug reports Apport see Bugs/ApportRetraces.


CategoryBugSquad CategoryDebugging

DebuggingProgramCrash (last edited 2022-12-20 22:13:06 by sergiodj)