diff options
| author | cevans@chromium.org <cevans@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-01-21 05:02:17 +0000 |
|---|---|---|
| committer | cevans@chromium.org <cevans@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-01-21 05:02:17 +0000 |
| commit | f355c56028d0404855185541c7ba8568c22ed4a3 (patch) | |
| tree | 8efc61aef651b72aacc3dd9084b3df0fdbf936d0 /base/debug/debugger_posix.cc | |
| parent | 20305ec6f1acf21392c2f3938a14a96f1e28e76d (diff) | |
| download | chromium_src-f355c56028d0404855185541c7ba8568c22ed4a3.zip chromium_src-f355c56028d0404855185541c7ba8568c22ed4a3.tar.gz chromium_src-f355c56028d0404855185541c7ba8568c22ed4a3.tar.bz2 | |
Make sure the process is _really_ gone after a __debugbreak(). We've had a
few annoying cases where someone has been monitoring Chrome under windbg,
which can skip over __debugbreak() and then show them a scary-looking
access violation.
BUG=NONE
TEST=NONE
Review URL: http://codereview.chromium.org/6372008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@72107 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/debug/debugger_posix.cc')
| -rw-r--r-- | base/debug/debugger_posix.cc | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/base/debug/debugger_posix.cc b/base/debug/debugger_posix.cc index b865e65..2eacaf9 100644 --- a/base/debug/debugger_posix.cc +++ b/base/debug/debugger_posix.cc @@ -174,6 +174,9 @@ bool BeingDebugged() { void BreakDebugger() { DEBUG_BREAK(); +#if defined(NDEBUG) + _exit(1); +#endif } } // namespace debug |