First, thanks for writing remote_pdb! It works very well to set breaks in child processes in normal circumstances.

There seems to be a communication problem when the main python program is under control of a program such as entr or when the main program is launched from ipython and sets it's own process group.

Could you please take a look at the question I posted a couple of days ago on SO? It's rather long so I won't repost the contents here.

http://stackoverflow.com/questions/43823564/python-3-debug-child-process-running-under-control-of-entr

Thanks, Mike Ellis

Hi,

I started using remote-pdb a few days ago and i noticed that the [TAB] action does not work under linux. I am not sure if this is the case on other OSes too. After telnet'ing when i press [TAB] the cursor just moves forward with a tab space.

i think it would be really cool if the TAB completion works via telnet.

i hope this will be takes into account and implemented, i'll be happy to contribute with some of my time in case i can be helpful.

Best,

Hi!

This PR adds testing for newer Python versions, as well as a workaround for a CPython bug in Python 3.6.6 and up.

It works for me locally, but there are a lot of tox environments and I have only run a subset of them. I'll fix any errors that come up, but if you have any concerns please do holler.

Cheers, love the software,

Matt

Hi, I was looking at doing a similar change as a PR for pudb and was looking at your source.

Going by your usage instructions - is there any reason to use the RemotePdb class when calling set_trace() with the same parameters seems to take care of that for you?

Thanks!

I just started using remote-pdb and run into an issue. If I run the debugger inside a running Docker container I am not able to establish a persistent connection with the debugger from the host. If I start a shell inside the docker container and run nc -vv localhost 4444 I obtain the expected prompt:

localhost (127.0.0.1:4444) open
> [My code breakpoint info]
(Pdb) 

But if I run the same from the host, the connection is terminated immediately:

$ nc -vv localhost 4444
Notice: Real hostname for localhost [127.0.0.1] is workbox1
localhost [127.0.0.1] 4444 (krb524) open
Total received bytes: 0
Total sent bytes: 0

I'm mapping host port 4444 to guest:4444, and I tried other mappings to ensure that was not the problem, but I get the same result consistently.

I am using Python 3.7's breakpoint() command. I have the following env variables read by Docker:

PYTHONBREAKPOINT=remote_pdb.set_trace
REMOTE_PDB_HOST=127.0.0.1
REMOTE_PDB_PORT=4444

My host is Arch linux (GNU netcat 0.7.1) and the guest is Alpine (nc part of Busybox 1.30.1). I can reproduce the same issue with socat and telnet.

This is an increedibly useful tool and if I could use it from the host it would be so much more efficient. Any help is appreciated.

Could the project description include a brief statement about whether or not the debugger should function under Jython 2.7.2 ? I see Python 2.7 badge but I know Jython is a bit weird.

pdbpp==0.10.2 remote-pdb==2.0.0 Python==3.8.0

The strangest thing. If I install pdbpp and remote-pdb, the first remote debugging session does not use pdbpp. Subsquent sessions it works.

What could be going wrong here?

I'm using this module together with pdbpp. This promises to offer the sticky option of pdbpp also for remote sessions.

One problem however seems to be that the terminal size is for some reason fixed and this results in not all the code being shown.

I'm posting this here just to start the conversation, it if possible this might be a pdbpp issue.

cool tool!

I'm playing around with curses right now and a remote debugger is exceptionally good for this -- the one thing that's a bit unfortunate is remote-pdb will always print output breaking the curses output:

would you accept a PR which allows an option (and environment variable) to silence this?

By configuring "cry" messages to use the "remote_pdb" logger instead of the root logger, a consumer can suppress duplicate messages if the root logger is also configured to log to STDERR

Is it possible to attach the PyCharm debugger to a process waiting after executing "RemotePdb("0.0.0.0", 5005).set_trace()"?

If so, how? I have tried every combination of remote, local, attach, run/debug config and anything else that I can find in the PyCharm UI but nothing seems cause it to connect. What is the PyCharm equivilent of "nc -C 127.0.0.1 5005"?

Hi Ionel, Thanks so much for making pyremotepdb, I use it as an alternate to GUI debuggers as I usually need to debug other processes over the network.

I was just wondering if it's a known issue (or limitation of telnet/nc) that one cannot use the Up arrow keyboard shortcut to reload the last run command. Indeed none of the arrow keys work, simple keyboard shortcuts don't work in my case. (all on Linux, kubuntu 18, etc). I'm not intimately familiar with how stdin works so perhaps this is a limitation that can't be overcome? Would be a shame, I'd love to have remotepdb work just like pdb.

cheers,

use case:

>>> import remote_pdb as rpdb
>>> rpdb.set_trace('./t.sock')
>>> rpdb.set_trace('t.sock', unixsocket=True)
>>> rpdb.set_trace(unixsocket='t.sock')

invalid:

>>> import remote_pdb as rpdb
>>> rpdb.set_trace('t.sock')
socket.gaierror: [Errno -2] Name or service not known

When invoked as a script, pdb will automatically enter post-mortem debugging if the program being debugged exits abnormally. After post-mortem debugging (or after normal exit of the program), pdb will restart the program. Automatic restarting preserves pdb’s state (such as breakpoints) and in most cases is more useful than quitting the debugger upon program’s exit.