Troubles using realgud:trepan3k as a client to a remote session

[dangirsh]

I found this bug while trying to use the realgud interface to connect to a remote trepan server.

On the remote I have:

def start_debugger_server():
    from trepan.interfaces import server as Mserver
    from trepan.api import debug
    connection_opts={'IO': 'TCP', 'PORT': 1955}
    intf = Mserver.ServerInterface(connection_opts=connection_opts)
    dbg_opts = {'interface': intf}
    print('Starting TCP server listening on port 1955.')
    debug(dbg_opts=dbg_opts)

(taken directly from the docs)

and the client uses:

(realgud:trepan3k "trepan3k --client --port 1955")

I've successfully connected to the remote this way, but hit two issues:

1. I have to manually help trepan find the file to track whenever it changes (e.g. I step into a function in a new file). In the case I point it to the remote copy in a TRAMP buffer, it loses track of the file after every "next"command.
2. If I issue a quit command, subsequent attempts to reconnect a client (after start_debugger_server was re-triggered) fail to connect. I get a window showing:

Current directory: /home/dan/canopy/
Command: trepan3k --client --port 1955
Connected.

but it's not talking to the server.

These issues make me think the realgud interface hasn't been tested much with the --client option. Has anybody gotten this to work?

[rocky]

I honestly don't remember what I've trred and what I haven't. It is generally true that when I need something I often find I have to fix bugs that have crept in since the last time I did something.

And yes remote debugging is not something I do a lot of. Probably if I use it I do it from track-mode.