[lldb-dev] Spurious process state change events

Vadim Chugunov via lldb-dev lldb-dev at lists.llvm.org
Fri Jan 15 11:35:30 PST 2016

I have a Python script that drives LLDB (in async mode), with a
listener attached to the process.
On OSX, upon the launch, LLDB emits a eStateRunning process state
event, and then eventually eStateStopped - when a breakpoint is hit.
On Linux, however, the initial eStateRunning is immediately followed
by eStateStopped and another eStateRunning, without any intervention
on my part.  This messes things up for me somewhat, because my script
thinks that a breakpoint has been hit and tries examine state of the
So I have 2 questions:
- Is it supposed to happen?
- What would be the best way to filter out these spurious stop events?
  if is_linux and is_first_stop_event: ...  feels a bit hacky.


More information about the lldb-dev mailing list