summaryrefslogtreecommitdiffstats
path: root/chrome/plugin
diff options
context:
space:
mode:
authorcevans@chromium.org <cevans@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-01-21 05:02:17 +0000
committercevans@chromium.org <cevans@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-01-21 05:02:17 +0000
commitf355c56028d0404855185541c7ba8568c22ed4a3 (patch)
tree8efc61aef651b72aacc3dd9084b3df0fdbf936d0 /chrome/plugin
parent20305ec6f1acf21392c2f3938a14a96f1e28e76d (diff)
downloadchromium_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 'chrome/plugin')
-rw-r--r--chrome/plugin/plugin_main.cc4
1 files changed, 3 insertions, 1 deletions
diff --git a/chrome/plugin/plugin_main.cc b/chrome/plugin/plugin_main.cc
index 0dc0503..4268b0f 100644
--- a/chrome/plugin/plugin_main.cc
+++ b/chrome/plugin/plugin_main.cc
@@ -149,8 +149,10 @@ int PluginMain(const MainFunctionParams& parameters) {
BOOL result = run_security_tests(&test_count);
DCHECK(result) << "Test number " << test_count << " has failed.";
// If we are in release mode, crash or debug the process.
- if (!result)
+ if (!result) {
__debugbreak();
+ _exit(1);
+ }
}
FreeLibrary(sandbox_test_module);