diff options
| author | Paul Lawrence <paullawrence@google.com> | 2017-06-23 08:10:18 -0700 |
|---|---|---|
| committer | Paul Lawrence <paullawrence@google.com> | 2017-06-23 18:50:00 +0000 |
| commit | c0c56ec7ceb953b275d8f1772f9276e72eb693ea (patch) | |
| tree | efd304b34fc28d62355227b9bf097c0f8e5f7f23 /libc/malloc_hooks/malloc_hooks.cpp | |
| parent | d87e5aa769c7ff22d7301ef4a29db3c04d61c0cc (diff) | |
Expand Seccomp whitelist
This seccomp failure is in the fault handler:
05-25 12:03:25.042 10201 27425 27425 F DEBUG : backtrace:
05-25 12:03:25.042 10201 27425 27425 F DEBUG : #00 pc 00015380
/data/data/redacted/files/storage/lib/libcrashsdk.so
So whenever an app using this crash sdk crashes it looks like a seccomp
problem. Fixing this won't stop the apps crashing, but will make the
crash reports accurate and useful.
So yes, the bug below is already fixed, but this issue has come back 2
or 3 times with different apps (b/62090571, b/62874867). This change
doesn't fix that crash either, but again it improves the reporting.
Bug: 62947697
Test: Device boots, app still fails but no longer with SECCOMP error
Change-Id: Ie0f8dc965001c8bc43f6a545b35bdcd38f006213
Diffstat (limited to 'libc/malloc_hooks/malloc_hooks.cpp')
0 files changed, 0 insertions, 0 deletions