Closed Bug 968544 Opened 12 years ago Closed 8 years ago

Something like about:crashes for B2G developer builds

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jld, Unassigned)

Details

Currently, if you get a crash on a b2g developer build, the user experience isn't very good — you get an alert where you can click “Report” and send the dump off to Mozilla, which doesn't accomplish much because you have the symbols and Mozilla doesn't. If you don't, the dump is deleted. (There's also a modal dialog box in some cases, and if you're just trying to make it go away you can wind up changing the setting to “never send crash reports”, in which case they're immediately deleted.) What we should do is leave the minidump on the device (there's some kind of limit on how many are kept already, I think?) and have some kind of way for the developer to pull the minidumps and extract information. Tests already behave more or less this way, so the infrastructure should be mostly there. For an initial implementation, a script in the B2G repo that's run on the host should work — it's not the case for all development tools, but this is probably going to be more frequently useful to Gecko developers than to app developers, so that type of interface should be less of a problem.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.