DebuggingProgramCrash

Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2005-07-25 04:04:37 →
Size: 1036
Editor: S0106000000cc07fc
Comment: add category documentation
← Revision 3 as of 2005-09-28 11:29:47 → ⇥
Size: 1070
Editor: i577B1901
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
handle SIG33 pass nostop noprint

  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:

    1. Install the build-time dependencies for the package: 

      sudo apt-get build-dep <package>

    2. Build .debs for debugging: 

      DEB_BUILD_OPTIONS="nostrip noopt" sudo apt-get source -b <package>

    3. Install the needed .debs (they will be in the current working directory if the build succeeded): 

      sudo dpkg --install <package.deb>

  3. Start the program under control of gdb: 

    gdb <program>
handle SIG33 pass nostop noprint
(gdb) run <arguments, if any>
  4. The program will start. Perform any actions necessary to reproduce the crash

  5. Retrieve a backtrace of the crash: 

    (gdb) thread apply all bt full
  6. 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

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