ack end's <TT>execute</TT> method. The debugger's (and so also the target's) actual I/O
    streams were hidden away within a GDB/MI wrapper.</P>

    <P>Each launcher script sets up a &mdash; usually Python &mdash; environment, launches the
    actual debugger, and provides a sequence of commands for it to load the Trace RMI plugin,
    connect back to Ghidra, launch the actual target process, and start the target trace. At this
    point, the plugin generally takes over, reacting to user and target events