<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi Jim,</div><div><br></div><div>I think you're right - a generalised hooking mechanism that could call arbitrary commands on various events would make more sense than a "template" mechanism. It would probably be easier to use than exposing the SBListener/SBBroadcaster stuff through the python API, and more useful than the current mechanism. </div><div><br></div><div>The current mechanism is useful for individual cases, but not for general cases the way that GDB's "hook-stop" macro is. The inspiration for this tool came from fractalg's .gdbinit script[1], which (among other things) defines a stop hook that prints a bunch of nicely formatted context information whenever the debugger stops - registers, some disassembly, whether the branch will be taken if the current instruction is a branch, etc. It just defines a single stop-hook and does some magic based on what architecture the current target is. If I want to do this with LLDB it seems that I would have to manually add a stop-hook to every target.</div><div><br></div><div><blockquote type="cite">(lldb) hook add target.create --arch x86_64 --executable-name MyProg --platform-name remote-macosx<br>Enter Target Create hook code, type DONE when done</blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">hook add process.stop-hook -o "voltron update"<br>DONE</blockquote></blockquote></blockquote></blockquote><div><br></div><div>This looks good to me. If this had something like the -f option in `command script` for calling a python function directly it would be even better :D</div><br><blockquote type="cite">Note, if we're going to do this, I'd also like to move the target stop-hooks into a general hook mechanism. And you could add "process created/died" "shared library loaded" and "thread created/died" hooks for platforms that track this. Some of these already get published by the event system, for those these "life cycle" hooks would just provide a convenient way to access the events from the command line.<br></blockquote><div><br></div><div>Yeah this would be great.</div><div><br></div><div>Cheers,</div><div>Loukas</div><div><br></div><div>[1] <a href="https://github.com/gdbinit/Gdbinit">https://github.com/gdbinit/Gdbinit</a></div><div><br></div><br><blockquote type="cite"><blockquote type="cite"><br><br>On 10/10/2013, at 3:58 AM, <a href="mailto:jingham@apple.com">jingham@apple.com</a> wrote:<br><br><blockquote type="cite">Right now, having multiple listeners getting process events doesn't really work. So if you have both the driver listening to process events, and you try to peek at them from your code as well, that very likely will cause problems.<br><br>It wouldn't be impossible to make this work. There is some asymmetry in process events, since some work goes on when the event is first fetched off the public queue (breakpoint commands get run, etc.) So you'd have to be careful to make sure that work doesn't get re-done. But it still could be made to work if needed. It is on our queue of things to clean up, but not high on the list...<br><br>Jim<br><br>On Oct 9, 2013, at 9:45 AM, <a href="mailto:snare@ho.ax">snare@ho.ax</a> wrote:<br><br><blockquote type="cite">Hi Yin,<br><br>Voltron is not so much built "on top" of LLDB as it is "glued to the side". You still use the main LLDB CLI for interaction with the debugger, voltron just spins off a background thread to send out data updates to client views (e.g. stack view, register view, etc). Have a look at the screenshot on the github page and you'll see what I mean (though the screenshot is GDB): <a href="https://github.com/snarez/voltron">https://github.com/snarez/voltron</a><br><br>As such, it does not control everything that goes into and comes out of the CLI, so parsing the output isn't an option.<br><br>Loukas<br><br>On 10/10/2013, at 3:36 AM, "Yin Ma" <<a href="mailto:yin@affinic.com">yin@affinic.com</a>> wrote:<br><br><blockquote type="cite">Hi Loukas,<br><br>We are also developing a terminal-based GUI for lldb. Our<br>Approach is to check the output from lldb to detect<br>The status change. So far it seems working fine. <br>Could you let me know why you use listener approach?<br>Do you get any case that parsing output doesn't work?<br><br>Thanks,<br><br>Yin<br><br>-----Original Message-----<br>From: <a href="mailto:lldb-dev-bounces@cs.uiuc.edu">lldb-dev-bounces@cs.uiuc.edu</a> [mailto:lldb-<a href="mailto:dev-bounces@cs.uiuc.edu">dev-bounces@cs.uiuc.edu</a>] On Behalf Of Malea, Daniel<br>Sent: Wednesday, October 09, 2013 8:20 AM<br>To: <a href="mailto:snare@ho.ax">snare@ho.ax</a>; <a href="mailto:lldb-dev@cs.uiuc.edu">lldb-dev@cs.uiuc.edu</a><br>Cc: Redmond, Paul<br>Subject: Re: [lldb-dev] Python API<br><br>Hi Loukas,<br><br>I too have been working on a terminal UI for LLDB (but not GDB) with some<br>colleagues (CC'd). I will commit what we have thus far shortly and you can<br>see what we did, and maybe share some efforts/ideas.<br><br>BTW, in terms of listeners, we initialize them like so:<br><br>self.listener = debugger.GetListener()<br><br> self.listener.StartListeningForEventClass(self.debugger,<br>lldb.SBTarget.GetBroadcasterClassName(),<br>| lldb.SBTarget.eBroadcastBitBreakpointChanged<br>| lldb.SBTarget.eBroadcastBitWatchpointChanged<br> )<br><br> self.listener.StartListeningForEventClass(self.debugger,<br><br>lldb.SBThread.GetBroadcasterClassName(),<br><br>lldb.SBThread.eBroadcastBitStackChanged<br>| lldb.SBThread.eBroadcastBitThreadSuspended<br>| lldb.SBThread.eBroadcastBitThreadResumed<br>| lldb.SBThread.eBroadcastBitSelectedFrameChanged<br>| lldb.SBThread.eBroadcastBitThreadSelected<br> )<br><br> self.listener.StartListeningForEventClass(self.debugger,<br>lldb.SBProcess.GetBroadcasterClassName(),<br>lldb.SBProcess.eBroadcastBitStateChanged<br>| lldb.SBProcess.eBroadcastBitInterrupt<br>| lldb.SBProcess.eBroadcastBitSTDOUT<br>| lldb.SBProcess.eBroadcastBitSTDERR<br>| lldb.SBProcess.eBroadcastBitProfileData<br> )<br> self.listener.StartListeningForEventClass(self.debugger,<br>lldb.SBCommandInterpreter.GetBroadcasterClass(),<br>lldb.SBCommandInterpreter.eBroadcastBitThreadShouldExit<br>| lldb.SBCommandInterpreter.eBroadcastBitResetPrompt<br>| lldb.SBCommandInterpreter.eBroadcastBitQuitCommandReceived<br>| lldb.SBCommandInterpreter.eBroadcastBitAsynchronousOutputData<br>| lldb.SBCommandInterpreter.eBroadcastBitAsynchronousErrorData<br> )<br><br><br><br><br>Cheers,<br>Dan<br><br><br><br>On 2013-10-09 10:13 AM, "<a href="mailto:snare@ho.ax">snare@ho.ax</a>" <<a href="mailto:snare@ho.ax">snare@ho.ax</a>> wrote:<br><br><blockquote type="cite">Hi,<br><br>I've been working on a terminal-based UI for LLDB (and GDB)[1] recently<br>and I have a few questions about the Python API.<br><br>The way this tool works currently is by registering a new command that<br>sends updates to client views, and then registering a stop-hook that<br>calls that command whenever the debugger stops.<br><br>From looking at the sample python code and the LLDB source I think maybe<br>I could do the same thing using SBListener/SBBroadcaster/etc.<br><br>I've tried stuff like this:<br><br>listener = lldb.SBListener()<br>listener.StartListeningForEventClass(lldb.debugger, 'lldb.process',<br>0xffffffff)<br>while 1:<br>if listener.WaitForEvent(1, event):<br> print('got event: ' + event.GetDataFlavor())<br><br>But I don't get notifications for processes starting and stopping.<br><br>I've also tried stealing lldb.debugger's listener:<br><br>listener = lldb.debugger.GetListener()<br><br>Š but that hangs when I get the first event. I suspect maybe that's a<br>terrible idea, and not how it's meant to be done when the LLDB CLI has<br>created the SBDebugger instance and its listener.<br><br>Is it possible to do this from a script run within an existing LLDB<br>instance? It seems like all the sample code doing things like this is<br>actually instantiating the SBDebugger itself and fully automating the<br>debugging session, rather than being imported into LLDB and running from<br>there. <br><br>I'd also like to receive notifications for the following events:<br>- a new file being loaded<br>- a target being run<br>- a target exiting<br><br>Thanks,<br>Loukas<br><br>[1] <a href="https://github.com/snarez/voltron">https://github.com/snarez/voltron</a><br><br><br>_______________________________________________<br>lldb-dev mailing list<br><a href="mailto:lldb-dev@cs.uiuc.edu">lldb-dev@cs.uiuc.edu</a><br>http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev<br></blockquote><br><br>_______________________________________________<br>lldb-dev mailing list<br><a href="mailto:lldb-dev@cs.uiuc.edu">lldb-dev@cs.uiuc.edu</a><br>http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev<br><br></blockquote><br><br>_______________________________________________<br>lldb-dev mailing list<br><a href="mailto:lldb-dev@cs.uiuc.edu">lldb-dev@cs.uiuc.edu</a><br>http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev<br></blockquote><br></blockquote></blockquote><br></blockquote></div><br></body></html>