DebuggingProgramCrash

Differences between revisions 2 and 16 (spanning 14 versions)
⇤ ← Revision 2 as of 2005-07-25 04:04:37 →
Size: 1036
Editor: S0106000000cc07fc
Comment: add category documentation
← 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:
  a. Install the build-time dependencies for the package: {{{
sudo apt-get build-dep <package>
}}}
  a. Build .debs for debugging: {{{
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 dpkg --install <package.deb>
}}}
 1. Start the program under control of `gdb`: {{{
gdb <program>
(gdb) run <arguments, if any>
}}}
 1. The program will start. Perform any actions necessary to reproduce the crash
 1. Retrieve a backtrace of the crash: {{{
(gdb) thread apply all bt full }}}

 1. Include the complete output from gdb in your bug report

* 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)