If you want the event handler to work for you and you don't mind the async output to stdout/err at any moment, then you can currently use the built in event loop, but just the event loop isn't exported as an option you can run in a separate thread. You can add an API to SBDebugger that is something like:
bool SBDebugger::SpawnEventHandlingThread(); And then run that. Is that what you were looking for? That would be a viable API to vend through SBDebugger. On Jul 18, 2014, at 6:22 PM, snare <[email protected]> wrote: >> >>> So if you don't want it to do that and provide the feedback just like the >>> command line tool, then you should be running your own event loop. >> >> Yeah this is what I’m trying to avoid, as above. > > Actually, that’s not right - I’m fine with running the event loop, I’d just > rather not have to reimplement the entire CLI. > > Loukas > _______________________________________________ > lldb-dev mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
_______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
