Steve Fink <sf...@mozilla.com> writes: > On 07/05/2016 01:33 AM, Julian Hector wrote: >> If you encounter a crash that may be due to seccomp, please file a bug in >> bugzilla and block Bug 1280415, we use it to track issues experienced on >> nightly. > > What would such a crash look like? Do they boil down to some system > call returning EPERM?
The relatively short version: it raises SIGSYS, and the signal handler can take arbitrary actions (e.g., polyfilling open() to message an out-of-process broker instead), but the default is currently to log a message to stderr, invoke the crash reporter[*], and terminate the process. --Jed [*] Also dumps the C stack directly if the crash reporter isn't available, and the JS stack in either case; both of these are unsafe if the syscall was in async signal context or had important locks held, but you were crashing anyway. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform