DebuggingProgramCrash

Differences between revisions 13 and 16 (spanning 3 versions)
⇤ ← Revision 13 as of 2006-05-09 22:30:59 →
Size: 1167
Editor: 196
Comment:
← Revision 16 as of 2006-06-19 16:06:44 → ⇥
Size: 65
Editor: 127
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
 1. Check if the package has a debugging version available. In general, debugging packages will be named with a `-dbg` suffix
 1. If not, you can generally* build one this way:

   * 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

  a. Install the development scripts: {{{
sudo apt-get install devscripts
}}}
  a. Install the build-time dependencies for the package: {{{
sudo apt-get build-dep <package>
}}}
  a. Build .debs for debugging: {{{
export DEB_BUILD_OPTIONS="nostrip noopt"
sudo apt-get source -b <package>
}}}
  a. Install the needed .debs (they will be in the current working directory if the build succeeded): {{{
sudo debi <package>*.changes
}}}
 1. Now you make a ["Backtrace"].
 1. You can also run ["Valgrind"], if the program crashes with a "Segmentation fault" or "Bus error".
 1. 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		 #REFRESH 0 http://help.ubuntu.com/community/DebuggingProgramCrash

DebuggingProgramCrash (last edited 2026-01-27 15:38:17 by sombrafam)