DebuggingProgramCrash

Differences between revisions 22 and 23
Revision 22 as of 2006-10-10 08:43:41
Size: 1485
Editor: i577B0D77
Comment:
Revision 23 as of 2006-10-10 08:45:02
Size: 1606
Editor: i577B0D77
Comment:
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:

=== References ===

 * Announce: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2006-September/000195.html

Add the following line to /etc/apt/sources.list:

deb http://people.ubuntu.com/~pitti/ddebs edgy main universe

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

sudo apt-get install yelp-dbgsym
  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"].

References

Old notes

  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
    2. Install the build-time dependencies for the package:

      sudo apt-get build-dep <package>
    3. Build .debs for debugging:

      export DEB_BUILD_OPTIONS="debug nostrip noopt"
      fakeroot apt-get source -b <package>
    4. Install the needed .debs (they will be in the current working directory if the build succeeded):

      sudo debi <package>*.changes

* most of the packages support the build of debugging version in this way. If that doesn't work for a package you can open a bug against it.


CategoryBugSquad

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