From 6897dfa16424defeb69850118d5a822cf38d05ed Mon Sep 17 00:00:00 2001 From: hjk Date: Tue, 12 Jul 2016 15:34:40 +0200 Subject: [PATCH] Debugger: Remove 'nopass' on SIGSEGV GDB handler This has been used since the dawn of time but seems to cause problems with JVM code. Task-number: QTCREATORBUG-16565 Change-Id: Iae8a2949671d162f84b9dfe954c8dfbbd743a8de Reviewed-by: Sandro Mani Reviewed-by: Orgad Shaneh --- src/plugins/debugger/gdb/gdbengine.cpp | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/src/plugins/debugger/gdb/gdbengine.cpp b/src/plugins/debugger/gdb/gdbengine.cpp index a2be1e5cfa9..adc486fb39b 100644 --- a/src/plugins/debugger/gdb/gdbengine.cpp +++ b/src/plugins/debugger/gdb/gdbengine.cpp @@ -4067,17 +4067,6 @@ void GdbEngine::startGdb(const QStringList &args) //runCommand("set overload-resolution off"); //runCommand(_("set demangle-style none")); - // From the docs: - // Stop means reenter debugger if this signal happens (implies print). - // Print means print a message if this signal happens. - // Pass means let program see this signal; - // otherwise program doesn't know. - // Pass and Stop may be combined. - // We need "print" as otherwise we will get no feedback whatsoever - // when Custom DebuggingHelper crash (which happen regularly when accessing - // uninitialized variables). - runCommand({"handle SIGSEGV nopass stop print"}); - runCommand({"set unwindonsignal on"}); runCommand({"set width 0"}); runCommand({"set height 0"});