================
@@ -491,17 +493,18 @@ bool GDBRemoteCommunicationClient::GetVContSupported(char
flavor) {
m_supports_vCont_S = eLazyBoolNo;
if (SendPacketAndWaitForResponse("vCont?", response) ==
PacketResult::Success) {
- const char *response_cstr = response.GetStringRef().data();
- if (::strstr(response_cstr, ";c"))
+ std::string response_str(response.GetStringRef());
+ response_str += ';';
+ if (response_str.find(";c;") != std::string::npos)
m_supports_vCont_c = eLazyBoolYes;
- if (::strstr(response_cstr, ";C"))
+ if (response_str.find(";C;") != std::string::npos)
----------------
DavidSpickett wrote:
I got confused here because the spec says:
```
‘C sig’
Continue with signal sig. The signal sig should be two hex digits.
```
However the supported response, I assume, is just `C`.
Or in other words: `C` means it can continue with any signal number. Rather
than `C<N>` meaning it can continue with some specific signal number.
https://github.com/llvm/llvm-project/pull/182287
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
