Closed
Bug 1029550
Opened 10 years ago
Closed 10 years ago
Generate ANR report when we fail due to timeout
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1027802
People
(Reporter: snorp, Assigned: gbrown)
References
Details
In mochitest/reftest/whatever, we sometimes hang, which manifests as a timeout failure. It would be very useful if we sent the process a SIGQUIT in these instances, which causes an ANR report to be generated. I am not sure about 4.0, but on recent Android versions these contain both native and managed stack traces, so it would be very helpful in finding out what caused the hang.
Comment 1•10 years ago
|
||
gbrown just literally filed a bug about this. SIGQUIT is what you want? On desktop we SIGABRT which triggers Breakpad. (Either way should be simple.)
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #1) > gbrown just literally filed a bug about this. SIGQUIT is what you want? On > desktop we SIGABRT which triggers Breakpad. (Either way should be simple.) Yeah, SIGQUIT triggers the Android ANR machinery. It sounds like following that with a SIBABRT is not a bad idea either.
Assignee | ||
Comment 3•10 years ago
|
||
Let's combine...
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•