I forgot to mention that this is running on a remote system, using a custom script to tar up everything needed, copy it over, run it, and pipe the output back to the originating terminal. It's a PITA to do this manually.

It's also a requirement to run on the remote system, as custom devices and other hardware are there (these are formal test scripts).

I'm quite familiar with the interactive use of the debugger, and would prefer to do that, but it's much easier to s/// the code and print line numbers. (OP updated).