DebuggingProgramCrash

Differences between revisions 13 and 14
⇤ ← Revision 13 as of 2006-05-09 22:30:59 →
Size: 1167
Editor: 196
Comment:
← Revision 14 as of 2006-05-09 22:32:19 → ⇥
Size: 1148
Editor: 196
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
   * Somthing to keep in mind, If you would like to create a build, bare in mind that you're going to need to have the relevant deb-src lines in your /etc/apt/sources.list    * Somthing 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. 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:
    • Somthing 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="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 ["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.

CategoryDocumentation

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