Skip to content
Permalink
Browse files

[lldb] [Process/gdb-remote] Fix defaulting signal to invalid in actio…

…n 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
  • Loading branch information...
mgorny committed Sep 17, 2019
1 parent 48de660 commit e4d25e9e16278d7926ec43c6ea7571e869d0a619
Showing with 3 additions and 2 deletions.
  1. +3 −2 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;
}
}

0 comments on commit e4d25e9

Please sign in to comment.
You can’t perform that action at this time.