llvmbot wrote:

<!--LLVM PR SUMMARY COMMENT-->

@llvm/pr-subscribers-lldb

Author: Ayush Sahay (ayushsahay1837)

<details>
<summary>Changes</summary>

Currently, GDBRemoteCommunicationServerLLGS::Handle_qfThreadInfo asserts if the 
number of processes under debug isn’t 1 and the multiprocess feature isn’t 
supported. This is so that we don't string IDs of threads belonging to 
different processes together without including the IDs of the processes 
themselves in the response when there are multiple processes under debug. 
However, it’s conceivable that we have no process under debug and the 
multiprocess feature isn’t supported. So, have 
GDBRemoteCommunicationServerLLGS::Handle_qfThreadInfo assert if the number of 
processes under debug is greater than 1 and the multiprocess feature isn’t 
supported.

---
Full diff: https://github.com/llvm/llvm-project/pull/88279.diff


1 Files Affected:

- (modified) 
lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp 
(+1-1) 


``````````diff
diff --git 
a/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp 
b/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp
index 3d37bb226a65fd..ae1a77e5be8321 100644
--- 
a/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp
+++ 
b/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp
@@ -2087,7 +2087,7 @@ void GDBRemoteCommunicationServerLLGS::AddProcessThreads(
 GDBRemoteCommunication::PacketResult
 GDBRemoteCommunicationServerLLGS::Handle_qfThreadInfo(
     StringExtractorGDBRemote &packet) {
-  assert(m_debugged_processes.size() == 1 ||
+  assert(m_debugged_processes.size() <= 1 ||
          bool(m_extensions_supported &
               NativeProcessProtocol::Extension::multiprocess));
 

``````````

</details>


https://github.com/llvm/llvm-project/pull/88279
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to