Thanks for the clarification. I’ve closed the bug after confirming my test
works when not in async mode.
However, in async mode what do I need to do to handle the stop events? I have
a loop that polls for events, and I see
0x7f965c000940 Event: broadcaster = 0x2a8c488 (lldb.process), type = 0x00000001
(state-changed), data = { process = 0x2a8c450 (pid = 31924), state = stopped}
After I call ‘run’, and it hits the breakpoint. What needs to be updated at
this point to allow me to ‘continue’?
Thanks,
Ben
From: [email protected] [mailto:[email protected]]
Sent: Thursday, May 16, 2013 7:07 PM
To: Langmuir, Ben
Subject: [Bug 16039] Cannot use 'continue' from the python api on Linux
Jim Ingham<mailto:[email protected]> changed bug
16039<http://llvm.org/bugs/show_bug.cgi?id=16039>
What
Removed
Added
CC
[email protected]<mailto:[email protected]>
Comment # 2<http://llvm.org/bugs/show_bug.cgi?id=16039#c2> on bug
16039<http://llvm.org/bugs/show_bug.cgi?id=16039> from Jim
Ingham<mailto:[email protected]>
This actually is just a script error. When you create a new debugger by
default it is running in "async" mode. In that mode, you have to handle the
stop events from running the target by hand. If you don't want to do that
work, then just set the debugger to async mode with:
debugger.SetAsync(False)
If you do that, then your script runs correctly, at least on Mac OS X.
________________________________
You are receiving this mail because:
* You reported the bug.
_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
