Merge lp:~ted/apport/backtrace into lp:~apport-hackers/apport/trunk

[Ted Gould]

Small little script to get a backtrace from a crash file.

[Martin Pitt (pitti)]

This is already provided by "apport-retrace -s foo.crash", so not necessary. apport-retrace also offers a lot of other options, like temporarily instlaling the necessary ddebs, opening an interactive gdb session, etc.

review: Disapprove

[Ted Gould (ted)]

On Fri, 2010-09-17 at 07:01 +0000, Martin Pitt wrote:
> This is already provided by "apport-retrace -s foo.crash", so not
> necessary.. apport-retrace also offers a lot of other options, like
> temporarily instlaling the necessary ddebs, opening an interactive
> gdb session, etc.

Hmm, I didn't know about apport-retrace, and in fact didn't have it
installed. Any reason this isn't part of the standard install of
apport?

Also, it seems to need "Package" which I don't always have. Is that
avoidable?

  $ apport-retrace
-s /var/crash/_usr_bin_gnome-power-manager.1000.crash
report file does not contain one of the required fields: CoreDump
Package ExecutablePath

Where the apport-backtrace can work fine as it only uses CoreDump and
ExecutablePath.

[Martin Pitt (pitti)]

You can invoke it with -R (--rebuild-package-info) if you have a crash report which wasn't post-processed by the UI yet, i. e. does not yet have a Package: field.

Unmerged revisions

1790. By Ted Gould on 2010-09-16

Adding in a little program to get a backtrace from a crash file.

=== added file 'bin/apport-backtrace'
--- bin/apport-backtrace	1970-01-01 00:00:00 +0000
+++ bin/apport-backtrace	2010-09-16 17:11:43 +0000
@@ -0,0 +1,7 @@
+#!/bin/sh -e
+
+TMPDIR=$(mktemp -d)
+
+apport-unpack $1 $TMPDIR
+gdb -nx `cat $TMPDIR/ExecutablePath` -core $TMPDIR/CoreDump -ex 'backtrace full' -ex 'thread apply all backtrace full' -ex quit
+rm -rf $TMPDIR