Hi, when we interrupt a process (SBProcess::Stop()) while a thread is currently being traced due to a breakpoint, the process will be halted and the thread's stop reason will be eStopReasonTrace. Upon resuming the process, we get an eStateExited event and LLDB disconnects from the inferior.
This is unlikely to ever pop up when using the LLDB cli client or XCode. We have to interrupt and resuming the process at a high frequency, which increases the likelihood of a thread being traced due to a breakpoint or other reason. My question boils down to: What could be the reason for receiving an eStateExited event after resuming on a eStopReasonTrace stop event? I'll try to setup a simple C app and a Python script calling into the LLDB APis that reflects what we do in our code to illustrate and reproduce the issue. Thanks, Mario
_______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
