From c83b5afa9bbb04d64ddd61cfaeca0348a15bd623 Mon Sep 17 00:00:00 2001 From: Orgad Shaneh Date: Sun, 16 Sep 2018 12:38:29 +0300 Subject: [PATCH] Debugger: Support core input in custom thread names GDB doesn't provide thread-core on core dump debugging. Give the user the option provide it. Change-Id: I15eae0280243ce307b9045be33e4b28e9b9c64d0 Reviewed-by: hjk --- src/plugins/debugger/gdb/gdbengine.cpp | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/plugins/debugger/gdb/gdbengine.cpp b/src/plugins/debugger/gdb/gdbengine.cpp index f06ce3c12cc..e73f19443d0 100644 --- a/src/plugins/debugger/gdb/gdbengine.cpp +++ b/src/plugins/debugger/gdb/gdbengine.cpp @@ -3031,6 +3031,8 @@ void GdbEngine::handleThreadNames(const DebuggerResponse &response) for (const GdbMi &name : names.children()) { ThreadData thread; thread.id = name["id"].data(); + // Core is unavailable in core dump. Allow the user to provide it. + thread.core = name["core"].data(); thread.name = decodeData(name["value"].data(), name["valueencoded"].data()); handler->updateThread(thread); }