Fix MOZ_Assert and MOZ_Crash for Android

RESOLVED FIXED in mozilla14

Status

()

defect
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: cpeterson, Assigned: cpeterson)

Tracking

Trunk
mozilla14
ARM
Android
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

No description provided.
Android's stdio and stderr are directed to /dev/null. On Android, log MOZ_Assert message to adb logcat instead of fprintf(stderr).
Attachment #612953 - Flags: review?(mh+mozilla)
On Android, segfault in MOZ_Crash because raise(SIGABRT) is handled asynchronously.

When MOZ_Crash raises SIGABRT, the process does not die immediately. MOZ_Crash returns and the thread continues running. When all threads in the process receives a SIBABRT, the current thread's call stack will not point to MOZ_Crash. 

If we segfault in MOZ_Crash, we crash immediately and capture the current call stack pointing to MOZ_Crash. Android's dalvikvm and abort() segfault for the same reasons.
Attachment #612955 - Flags: review?(mh+mozilla)
Attachment #612953 - Flags: review?(mh+mozilla) → review+
Attachment #612955 - Flags: review?(mh+mozilla) → review+
Assignee: nobody → cpeterson
Status: NEW → ASSIGNED
https://hg.mozilla.org/mozilla-central/rev/8a7965116a33
https://hg.mozilla.org/mozilla-central/rev/42870fe1a4a3
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla14
You need to log in before you can comment on or make changes to this bug.