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.
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 _usr_bin_ gnome-power- manager. 1000.crash
-s /var/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.