diff options
| author | jeremy@chromium.org <jeremy@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-07-11 11:19:32 +0000 |
|---|---|---|
| committer | jeremy@chromium.org <jeremy@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-07-11 11:19:32 +0000 |
| commit | 64fb9acba969a51fc806df5ae8e3e60e05994b78 (patch) | |
| tree | f237cdd9716b147bab976a4dcfc26afada4ca712 /chrome/browser/renderer_host/render_process_host.h | |
| parent | 8e20ea65bca98e1f3b0b46a5b69f7726e7959f1c (diff) | |
| download | chromium_src-64fb9acba969a51fc806df5ae8e3e60e05994b78.zip chromium_src-64fb9acba969a51fc806df5ae8e3e60e05994b78.tar.gz chromium_src-64fb9acba969a51fc806df5ae8e3e60e05994b78.tar.bz2 | |
Mac: Fail early on Sandbox errors
We know that on certain machines the Seatbelt library is borked and even a simple test program that initializes the sandbox fails.
There is already a CHECK() in chrome_dll_main() that fires if the Sandbox didn't initialize correctly. This CL changes all sandbox failures to LOG(FATAL)s so we get different stack signatures when we crash.
BUG=44761
TEST=Browser & Unit tests should continue to function correctly.
Review URL: http://codereview.chromium.org/2861046
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@52058 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/renderer_host/render_process_host.h')
0 files changed, 0 insertions, 0 deletions