Make sure the process is _really_ gone after a __debugbreak(). We've had a...

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


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=72107

[Chris Evans, 2011-01-20 22:33:45]

As discussed.

[Cris Neckar, 2011-01-20 22:35:56]

LGTM

[Chris Evans, 2011-01-21 00:12:59]

On 2011/01/20 22:35:56, cdn wrote:
> LGTM

PTAL?

Added changes to the BreakDebugger() methods, which are called in the event of
CHECK(), LOG(FATAL), etc. -- and directly by the Mac OOM handlers.

We can't unconditionally exit because some of our debug helper code is using
BreakDebugger() to simply get the debugger attached when debugging.

[Cris Neckar, 2011-01-21 00:52:25]

This seems to work on windows as well

LGTM