From 08c952e53a4efcd5b50c0ec947bf216101c027ef Mon Sep 17 00:00:00 2001
From: isanae <14251494+isanae@users.noreply.github.com>
Date: Sat, 7 Nov 2020 19:05:15 -0500
Subject: stopped using core dump stuff from usvfs, mo has its own set
 exception handler at the start, it can handle not having qt or data paths
 hopefully fixed infinite crash dumps

---
 src/moapplication.cpp | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

(limited to 'src/moapplication.cpp')

diff --git a/src/moapplication.cpp b/src/moapplication.cpp
index 24cafd05..bb7b4922 100644
--- a/src/moapplication.cpp
+++ b/src/moapplication.cpp
@@ -188,8 +188,6 @@ int MOApplication::doOneRun(SingleInstance& singleInstance)
   const QString dataPath = currentInstance->directory();
   setProperty("dataPath", dataPath);
 
-  setExceptionHandlers();
-
   if (!setLogDirectory(dataPath)) {
     reportError("Failed to create log folder");
     InstanceManager::singleton().clearCurrentInstance();
@@ -272,7 +270,7 @@ int MOApplication::runApplication(
 
     // global crashDumpType sits in OrganizerCore to make a bit less ugly to
     // update it when the settings are changed during runtime
-    OrganizerCore::setGlobalCrashDumpsType(settings.diagnostics().crashDumpsType());
+    OrganizerCore::setGlobalCoreDumpType(settings.diagnostics().coreDumpType());
 
     env::Environment env;
     env.dump(settings);
-- 
cgit v1.3.1