ubuntu-phone team mailing list archive

[Ted Gould <ted@xxxxxxxxxx>]

On Sat, 2014-06-07 at 15:57 +0100, Alan Pope wrote:

> Unfortunately I get a bunch of crash files in /var/crash, and need to
> do some correlation to figure out which app crashed it. I'll modify my
> script to look for files in /var/crash after every application
> start/stop cycle and pause so I can analyse it.
> 
> e.g. these guys, no idea what triggered them without some effort.


Frankly, I don't think you should have to analyze them, though that'd be
nice. A lot of time stacktraces are self explanatory in that regard.
Uploading is more important that analyzing.


> I can file bugs for them, but do the devs want the crash files
> attached, or just run "apport-cli <crashfile>"? As a dev, what do you
> want from me when I spot one of these crashers?


For me personally I just want you to run:

/usr/share/apport/whoopsie-upload-all

That'll collect the additional apport data and put them into errors for
grouping. I imagine that most devs are checking errors for stack traces
of their packages already, and that way we can see if they happen on
specific devices/architectures/etc.

There's currently no tool to add a custom field on the crash reports
like "AlanTesting: Staring app" or similar. But I it shouldn't be too
hard to add at the top of the crash files with a small script. Then we
should be able to search for them by that key I believe (cc'd Evan to
check that)

Ted

Attachment: signature.asc
Description: This is a digitally signed message part