kusmour wrote: > `lost connection ` usually indicates lldb-server crasing. Is it what > happening in this situation? If so, we should harden lldb-server to not crash.
I have debugged lldb-server and it didn't crash. Instead it finished the and exit with status 0. From my investigation this is because the gdb-remote packets `vCont;c` was sent to resume the process then when asking for threads, I saw it triggered `\x03` (ctrl-c). Now the process will become unresponsive and ProcessGDBRemote got `eStateInvalid` leads to a "lost connection" then it just quit. https://github.com/llvm/llvm-project/pull/134339 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
