Closed
Bug 909534
Opened 11 years ago
Closed 11 years ago
asm.js signal handler should _exit() instead of exit()
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla26
People
(Reporter: khuey, Assigned: luke)
Details
Attachments
(3 files)
4.93 KB,
text/plain
|
Details | |
2.36 KB,
patch
|
bhackett1024
:
review+
|
Details | Diff | Splinter Review |
3.59 KB,
patch
|
bhackett1024
:
review+
|
Details | Diff | Splinter Review |
Running at/on_exit functions is a bad idea.
Assignee | ||
Comment 1•11 years ago
|
||
Ah, good point. The exit() call is intended to be, as the comment explains, a backstop and never actually executed. OOC, are you actually seeing this executed? In which branch?
Reporter | ||
Comment 2•11 years ago
|
||
ckitching was seeing it on Android after hitting a previous fatal assertion. Log coming up.
Reporter | ||
Comment 3•11 years ago
|
||
Assignee | ||
Comment 4•11 years ago
|
||
Could you 'p prevHandler->sa_sigaction' in the AsmJSFaultHandler (I'm hoping for a symbolic name here).
Assignee | ||
Comment 5•11 years ago
|
||
Also, looking at this handler again, it seems wrong to call exit() in the SA_SIGINFO branch: what if the chained handler fixes up the fault (like AsmJSFaultHandler does) or calls sigaction(..., NULL) and returns (like AsmJSFaultHandler does in the 'else' branch; so that the fault happens at the faulting instruction. I'll patch.
Assignee | ||
Comment 6•11 years ago
|
||
Assignee | ||
Comment 7•11 years ago
|
||
This is a small related cleanup I've been meaning to do: SIGBUS was only necessary for OSX and x86 segment prefixes.
Attachment #796203 -
Flags: review?(bhackett1024)
Updated•11 years ago
|
Attachment #796201 -
Flags: review?(bhackett1024) → review+
Updated•11 years ago
|
Attachment #796203 -
Flags: review?(bhackett1024) → review+
Assignee | ||
Comment 8•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/4543cebdc8a0 https://hg.mozilla.org/integration/mozilla-inbound/rev/e89815fe247d
Assignee | ||
Comment 9•11 years ago
|
||
Kyle: does this fix the problem for you?
Comment 11•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/4543cebdc8a0 https://hg.mozilla.org/mozilla-central/rev/e89815fe247d
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
Comment 12•11 years ago
|
||
So it appears that by default Bugzilla stops showing the needinfo flag when the bug is closed... You're too efficient! :P Yes, this seems to have fixed the problem. My more recent work isn't producing unbearably huge and confusing sequences of segfaults any more. (At least, not of length >1)
Flags: needinfo?(ckitching)
You need to log in
before you can comment on or make changes to this bug.
Description
•