There should be support for more reasons for a debugger to stop, like thread
creation, module loaded, etc.
I'm not sure how this works in Linux but the Windows Debug APIs provide
notification for these events.
This will be needed for full thread support and dynamically getting module
symbols (this is too expensive to do on every single step).
While the code already gets all thread IDs through this notification, it can't
propagate the info to the debugger/plugins.
Just like Olly this would also allow to automatically stop on one of these
events, e.g. stop everytime a new DLL is loaded.
Original issue reported on code.google.com by evan.teran on 3 Oct 2012 at 3:21
Original issue reported on code.google.com by
evan.teran
on 3 Oct 2012 at 3:21