forked from OSchip/llvm-project
[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
This commit is contained in:
parent
48de660bbf
commit
e4d25e9e16
|
@ -1383,7 +1383,8 @@ GDBRemoteCommunicationServerLLGS::Handle_C(StringExtractorGDBRemote &packet) {
|
||||||
packet, "unexpected content after $C{signal-number}");
|
packet, "unexpected content after $C{signal-number}");
|
||||||
}
|
}
|
||||||
|
|
||||||
ResumeActionList resume_actions(StateType::eStateRunning, 0);
|
ResumeActionList resume_actions(StateType::eStateRunning,
|
||||||
|
LLDB_INVALID_SIGNAL_NUMBER);
|
||||||
Status error;
|
Status error;
|
||||||
|
|
||||||
// We have two branches: what to do if a continue thread is specified (in
|
// We have two branches: what to do if a continue thread is specified (in
|
||||||
|
@ -3322,4 +3323,4 @@ std::string GDBRemoteCommunicationServerLLGS::XMLEncodeAttributeValue(
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
return result;
|
return result;
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue