From e79af02bb0e8de14c881f5071a519f6fadedc828 Mon Sep 17 00:00:00 2001 From: Herbert Dürr Date: Mon, 25 Nov 2013 13:29:47 +0000 Subject: Resolves: #i123747# allow treating Window's SEH events as C++ exceptions The crash reporter facility can provide much better details about crashes. But if that facility is disabled then handling SEH events such as div-by-zero as C++ exceptions is a worthwhile alternative. It can provide a few interesting details and it allows a graceful shutdown of the application. (cherry picked from commit c9d10b167b37a9cb0bb310cafc8e80b6cce8ea7a) Conflicts: sal/osl/w32/signal.cxx Change-Id: I25324d6e02ab8acd8fd2b036b77039aac87cf262 --- desktop/source/app/app.cxx | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) (limited to 'desktop/source/app') diff --git a/desktop/source/app/app.cxx b/desktop/source/app/app.cxx index ee3b4d5048f7..79fdc5048b4e 100644 --- a/desktop/source/app/app.cxx +++ b/desktop/source/app/app.cxx @@ -1488,11 +1488,8 @@ int Desktop::Main() // set static variable to enabled/disable crash reporter retrieveCrashReporterState(); - if ( !isCrashReporterEnabled() ) - { - osl_setErrorReporting( sal_False ); - // disable stack trace feature - } + const bool bCrashReporterEnabled = isCrashReporterEnabled(); + osl_setErrorReporting( !bCrashReporterEnabled ); // create title string LanguageTag aLocale( LANGUAGE_SYSTEM); -- cgit