HomeSort by relevance Sort by last modified time
    Searched refs:SANDBOX_DIE (Results 1 - 3 of 3) sorted by null

  /external/libchrome/sandbox/linux/seccomp-bpf/
sandbox_bpf.cc 115 SANDBOX_DIE(static_cast<const char*>(aux));
155 SANDBOX_DIE(
173 SANDBOX_DIE("Cannot start sandbox; "
178 SANDBOX_DIE("Cannot start sandbox; kernel does not support synchronizing "
258 SANDBOX_DIE("Kernel refuses to enable no-new-privs");
268 SANDBOX_DIE(
273 SANDBOX_DIE("Kernel refuses to turn on BPF filters");
die.h 15 #define SANDBOX_DIE(m) sandbox::Die::SandboxDie(m, __FILE__, __LINE__)
28 // Most users would want to call SANDBOX_DIE() instead, as it logs extra
33 // This method gets called by SANDBOX_DIE(). There is normally no reason
48 // We generally want to run all exit handlers. This means, on SANDBOX_DIE()
trap.cc 64 SANDBOX_DIE("Failed to block SIGBUS");
93 SANDBOX_DIE("Failed to configure SIGSYS handler");
108 SANDBOX_DIE("Failed to configure SIGSYS handler");
121 SANDBOX_DIE("Failed to allocate global trap handler");
187 // SANDBOX_DIE() can call LOG(FATAL). This is not normally async-signal
268 // This SANDBOX_DIE() can optionally be removed. It won't break security,
270 // to understand. Removing the SANDBOX_DIE() allows callers to easily check
273 SANDBOX_DIE(
305 SANDBOX_DIE("Too many SECCOMP_RET_TRAP callback instances");

Completed in 55 milliseconds