Closed Bug 932107 Opened 12 years ago Closed 12 years ago

Improve user experience for developers encountering sandbox violations

Categories

(Core :: Security, defect)

Product:
Core
Component:
Security
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 941375

People

(Reporter: jld, Unassigned)

References

Details

Right now, if you have a b2g "eng" build, a sandbox violation is reported with a single line in logcat, giving the system call number (not name) and the numeric value of the first argument (which might be a pointer). For development/testing purposes we should provide more information. Ideally, we should treat this the same way we'd treat a segmentation fault or MOZ_CRASH (if not better, because this can be caused by bugs in chrome script, not just C++). We may want this to happen before seccomp goes live in TBPL. It'd be especially nice if TBPL can automagically present useful information about the crash.
Whoops. Forgot I filed this one, and filed another one.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.