Consider not changing ctty and emulating signals instead about madbg HOT 2 OPEN

Thank you! I am working on a new major version for madbg, and getting rid of this behavior will be one of the main updates in it. Until then, I fixed your specific issue and published a new minor version - try madbg==1.3.1 and see if it solved your case 😄

from madbg.

I was going to open an bug, but then I saw this existing one (that at least seems to line up with the issue I encountered).
Python: 3.10.5
madbg: 1.2.0
I have an application running in uwsgi on another machine like so:

<uwsgi>
        <plugin>python310</plugin>
        <virtualenv>/home/me/venvs/serveframe</virtualenv>
        <wsgi-file>/home/me/www/u/serveframe.py</wsgi-file>
</uwsgi>

I added a breakpint like: madbg.set_trace(ip='my-ip', port=3513) and when I tried to connect to it from my PC with $ madbg connect my-ip 3513 it caused the application to crash. This is the end of the stack trace:

.../madbg/tty_utils.py", line 53, in attach_ctty
    fcntl.ioctl(fd, termios.TIOCSCTTY, 1)
PermissionError: [Errno 1] Operation not permitted

The line is

From ioctl_tty(2) I tried changing the third argument to 1 from 0, but it made no difference. I changed the line to just pass and was able to connect without an issue.

from madbg.