Upgrade Notes
- On a box behind an authenticating gateway,
lager debug NET gdbserverneeds a gateway with debug-tunnel support. The CLI now reaches the GDB port of such a box through its gateway. If the gateway is older, the command starts the GDB server and then stops with an error that the gateway does not support debug tunnels yet, and exits with status 1. Before this release it printed atarget remote <box>:<port>address that could not connect. Ask the administrator of the box to update its gateway. A plain Lager Box needs no change.
Features
lager debug NET gdbserverworks on a box behind an authenticating gateway. Such a box does not open its GDB port to the network, so GDB could not connect to it. The command now opens a tunnel through the gateway, listens onlocalhostonly, and stays in the foreground until Ctrl-C. Connect witharm-none-eabi-gdb -ex 'target remote localhost:2331'. GDB can disconnect and connect again while the tunnel is open. Ctrl-C closes only the tunnel: the GDB server continues to run on the box, andlager debug NET disconnectstops it. The command decides for each box whether a tunnel is necessary; on a plain Lager Box it behaves as before.- New
gdbserveroptions.--local-portselects a different local port for the tunnel.--no-tunnelstarts the GDB server and returns without a tunnel, for scripts. With--json, the output has atunnelobject withlocal_hostandlocal_port.
lager update for it.

