From e4d25e9e16278d7926ec43c6ea7571e869d0a619 Mon Sep 17 00:00:00 2001 From: Michal Gorny Date: Tue, 17 Sep 2019 09:31:00 +0000 Subject: [PATCH] [lldb] [Process/gdb-remote] Fix defaulting signal to invalid in action list Fix processing of "C" packet with signal for the whole process to default signal value for action list to LLDB_INVALID_SIGNAL_NUMBER rather than 0. Differential Revision: https://reviews.llvm.org/D67625 llvm-svn: 372090 --- .../Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp b/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp index ac579ef..63c89d0 100644 --- a/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp +++ b/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp @@ -1383,7 +1383,8 @@ GDBRemoteCommunicationServerLLGS::Handle_C(StringExtractorGDBRemote &packet) { packet, "unexpected content after $C{signal-number}"); } - ResumeActionList resume_actions(StateType::eStateRunning, 0); + ResumeActionList resume_actions(StateType::eStateRunning, + LLDB_INVALID_SIGNAL_NUMBER); Status error; // We have two branches: what to do if a continue thread is specified (in @@ -3322,4 +3323,4 @@ std::string GDBRemoteCommunicationServerLLGS::XMLEncodeAttributeValue( } } return result; -} \ No newline at end of file +} -- 2.7.4