Closed qrockz closed 5 months ago
I think the main problem here is one of documentation. You run first.py
with pudb, which creates a (non-remote) Debugger
instance. Initiating remote debugging creates another (remote) debugger instance. Since the debugger instance holds handles to various Urwid guts that differ based on remote/non-remote, the non-remote instance can't be reused. So while I agree that the error message is a bit opaque for non-insiders, it is accurate.
The fix should be simple: don't run first.py
with pudb
, just regular python
suffices.
It's an (IMO) valid question whether the message could provide better advice on what to do.
@inducer Thank you for your reply.
don't run first.py with pudb [...]
These were the keywords which gave me the hint!
$ python3 -m pdb first.py
Then jump to the first breakpoint() where pdb gives the hint to connect with telnet.
\o/
Just on more question:
How can I handle user input via telnet remote debugging?
remote debugging raises error:
To Reproduce code trying to debug: first.py
pudb first.py
trying to connect with other terminal to this session:
Versions