Op 25-9-2012 19:44, Jim Ingham schreef:
On Sep 25, 2012, at 6:43 AM, Carlo Kok <[email protected]> wrote:
I've figured out most of what i need from the LLDB api but have a few questions
I can't figure out myself:
* How do i get notified of "thread started", "thread finished" events?
We don't currently support thread started & thread finished.
Oke I guess I can do without just fine. I can enumerate them when I need
the list I guess.
* How do i find out when a breakpoint has been bound?
The target broadcasts "breakpoint changed" notifications. Note that lldb breakpoints
remain active as long as they are around and can be set on many locations, so they may be
"bound" more than once in the course of the debugging session. Anyway, you get the
target broadcaster, and attach a listener to that (listening for the event bit
eBroadcastBitBreakpointChanged) and wait on the listener. There are some static functions in
SBBreakpoint.h to decode the breakpoint changed events.
* How can I get notified of when a module is loaded?
The target also broadcasts these, the event bits are eBroadcastBitModulesLoaded
& Unloaded. These events don't contain any data, you have to look at the
module list to figure out what happened. We should add the list of modules changed
at some point.
* How do I stop a process when it's still running, "Stop" sets a breakpoint,
which isn't what i want. Disposing the debugger creates access violations.
Humm, Stop is the call to use, but it shouldn't need to set a breakpoint. How
are you seeing that?
I meant that it lokked like "stop" breaks the debugger where ever it is.
I want to kill off the process all together. IE stop debugging all together.
Thanks for the answers!
--
Carlo Kok
_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
