Skip to content
Permalink
Browse files

[lldb] [Process/gdb-remote] Correct more missing LLDB_INVALID_SIGNAL_…

…NUMBER

Correct more uses of 0 instead of LLDB_INVALID_SIGNAL_NUMBER.

Differential Revision: https://reviews.llvm.org/D67727

llvm-svn: 372300
  • Loading branch information...
mgorny committed Sep 19, 2019
1 parent 84dc688 commit c36b0bf31067b258af59b9f865cef5a091bf906f
Showing with 4 additions and 3 deletions.
  1. +4 −3 lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp
@@ -1454,7 +1454,8 @@ GDBRemoteCommunicationServerLLGS::Handle_c(StringExtractorGDBRemote &packet) {
}

// Build the ResumeActionList
ResumeActionList actions(StateType::eStateRunning, 0);
ResumeActionList actions(StateType::eStateRunning,
LLDB_INVALID_SIGNAL_NUMBER);

Status error = m_debugged_process_up->Resume(actions);
if (error.Fail()) {
@@ -1521,7 +1522,7 @@ GDBRemoteCommunicationServerLLGS::Handle_vCont(
ResumeAction thread_action;
thread_action.tid = LLDB_INVALID_THREAD_ID;
thread_action.state = eStateInvalid;
thread_action.signal = 0;
thread_action.signal = LLDB_INVALID_SIGNAL_NUMBER;

const char action = packet.GetChar();
switch (action) {
@@ -2724,7 +2725,7 @@ GDBRemoteCommunicationServerLLGS::Handle_s(StringExtractorGDBRemote &packet) {
return SendErrorResponse(0x33);

// Create the step action for the given thread.
ResumeAction action = {tid, eStateStepping, 0};
ResumeAction action = {tid, eStateStepping, LLDB_INVALID_SIGNAL_NUMBER};

// Setup the actions list.
ResumeActionList actions;

0 comments on commit c36b0bf

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