From a8c8192e3f4ef922465f0f1462fa4e1cd3fe2c8d Mon Sep 17 00:00:00 2001 From: Tor Lillqvist Date: Tue, 5 May 2020 19:15:52 +0300 Subject: On iOS, avoid catching exceptions to just immediately exit or abort anyway It is better to let the exception be uncaught and then catch that in the debugger. (Maybe even inspect its backtrace from a crash dump automatically sent from an end-user device.) Change-Id: Ice02d5cbd7f4a59eae7ce8a9fac47dec8b234a5e Reviewed-on: https://gerrit.libreoffice.org/c/core/+/93505 Tested-by: Jenkins CollaboraOffice Reviewed-by: Tor Lillqvist --- desktop/source/app/app.cxx | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'desktop') diff --git a/desktop/source/app/app.cxx b/desktop/source/app/app.cxx index 59d6a0db378f..dda31df281e9 100644 --- a/desktop/source/app/app.cxx +++ b/desktop/source/app/app.cxx @@ -1618,7 +1618,9 @@ int Desktop::Main() } // call Application::Execute to process messages in vcl message loop +#ifndef IOS try +#endif { #if HAVE_FEATURE_JAVA // The JavaContext contains an interaction handler which is used when @@ -1638,6 +1640,7 @@ int Desktop::Main() Execute(); } } +#ifndef IOS catch(const css::document::CorruptedFilterConfigurationException& exFilterCfg) { RequestHandler::SetDowning(); @@ -1663,6 +1666,7 @@ int Desktop::Main() RequestHandler::SetDowning(); FatalError( "Caught Unknown Exception: Aborting!"); } +#endif } else { -- cgit