Debugger: Fix post mortem action on Windows

Change-Id: I411853098f3bb7c410b4446bb6f2ed61fb11b217
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
Christian Stenger
2023-07-07 12:05:25 +02:00
parent 7d9b124ea2
commit 381ff44f66
2 changed files with 2 additions and 7 deletions

View File

@@ -29,11 +29,6 @@ public:
DebuggerSettings &s = settings();
setOnApply([&s] {
const bool originalPostMortem = s.registerForPostMortem->value();
const bool currentPostMortem = s.registerForPostMortem->volatileValue();
// explicitly trigger setValue() to override the setValueSilently() and trigger the registration
if (originalPostMortem != currentPostMortem)
s.registerForPostMortem->setValue(currentPostMortem);
s.page1.apply();
s.page1.writeSettings();
});

View File

@@ -405,6 +405,8 @@ DebuggerSettings::DebuggerSettings()
page1.registerAspect(&forceLoggingToConsole);
page1.registerAspect(&sourcePathMap);
if (HostOsInfo::isWindowsHost())
page1.registerAspect(registerForPostMortem);
// Page 4
page4.registerAspect(&useDebuggingHelpers);
@@ -429,8 +431,6 @@ DebuggerSettings::DebuggerSettings()
page5.registerAspect(&firstChanceExceptionTaskEntry);
page5.registerAspect(&secondChanceExceptionTaskEntry);
page5.registerAspect(&ignoreFirstChanceAccessViolation);
if (HostOsInfo::isWindowsHost())
page5.registerAspect(registerForPostMortem);
// Page 6
page6.registerAspect(&cdbSymbolPaths);