DebuggingProgramCrash

Differences between revisions 17 and 18
Revision 17 as of 2006-09-01 20:00:38
Size: 1247
Editor: ottawa-hs-206-191-33-252
Comment: Recreating here
Revision 18 as of 2006-09-01 20:02:59
Size: 1242
Editor: ottawa-hs-206-191-33-252
Comment:
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
CategoryDocumentation CategoryBugSquad
  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"
      sudo 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
  3. Now you make a [https://wiki.ubuntu.com/Backtrace Backtrace].

  4. You can also run [https://wiki.ubuntu.com/Valgrind Valgrind], if the program crashes with a "Segmentation fault" or "Bus error".

  5. Optionally, you may be asked to produce an [https://wiki.ubuntu.com/Strace Strace].

* 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 2026-01-27 15:38:17 by sombrafam)