DebuggingProgramCrash

Differences between revisions 20 and 21
⇤ ← Revision 20 as of 2006-09-01 20:20:13 →
Size: 1150
Editor: ottawa-hs-206-191-33-252
Comment:
← Revision 21 as of 2006-10-09 16:25:51 → ⇥
Size: 1154
Editor: stjhnf0111w-142162140177
Comment: sudo isn't necessary to build source packages... fakeroot will do.
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
sudo apt-get source -b <package> fakeroot apt-get source -b <package>

  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
  3. Now you make a ["Backtrace"].
  4. You can also run ["Valgrind"], if the program crashes with a "Segmentation fault" or "Bus error".
  5. Optionally, you may be asked to produce an ["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 2022-12-20 22:13:06 by sergiodj)