That was an oversight, they should definitely be available in Python. Their purpose is to keep the SB API user's notion of the selected thread in sync with the command-line's version. So they don't get broadcast when the SB API's directly change say the selected frame or the selected thread, only when the command line does. That means listening to these events won't require you do any extra work in your ordinary use of the SB API's. But if you were trying to write some UI for lldb in Python, and were planning to offer a way to invoke lldb commands as well, you would need these events. Jim
On Oct 3, 2013, at 1:13 PM, Malea, Daniel <[email protected]> wrote: > Hi all, > > I'm starting to hack on an alternative interface to LLDB, and I noticed the > Python SBThread interface is missing the BroadcasterBits enum and the > GetBroadcasterClassName static function. > > This tiny patch adds both of those missing things to the SBThread.i interface > file. OK to commit, or is it a bad idea to listen for thread events from > python? > > > Thanks, > Dan > <sbthread_broadcaster_interface.patch>_______________________________________________ > lldb-commits mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits _______________________________________________ lldb-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
