Andreas Klöckner
Andreas Klöckner
We'll need an example file to reproduce this bug in order to help you. Also, are you on Python2 or 3? What version of pudb?
Make that a variable and use it in both spots?
The debugger tries to live on the same stack as the "debuggee" that just ran out of stack space. It's likely that the Python runtime *enters* the debugger, but then...
https://en.wikipedia.org/wiki/Windows_Terminal claims that Windows Terminal (the new one, not the old "Command Prompt" thing) supports ANSI sequences now, so that might actually work. Could you try?
Thanks for trying and relaying the results. Could you try the curses display? (Edit `$HOME/.config/pudb/pudb.cfg` to set `display` to `curses`. The 3.x version specifics are outdated nonsense. I routinely use...
Does `import curses` succeed? It looks like you're still on the raw display: ``` File "C:\projects\tester\py34\lib\site-packages\urwid\raw_display.py", line 92, in __init__ fcntl.fcntl(self._resize_pipe_rd, fcntl.F_SETFL, os.O_NONBLOCK) ```
I'd be happy to consider PRs along these lines.
We do have a signal handler for ^C in an attempt to do something smarter than just show where the `KeyboardInterrupt` exception brought things to a halt. If you have...
Thanks for your contribution! I'm not completely sure about this functionality though. I think of a watch expression as something you add while poking around in a single function--and so...
Are you planning on making use of pudb's UI? If not, you're probably better off building on bdb, which is debugging functionality built into Python's standard library. pudb is built...