[issue14788] Pdb debugs itself after ^C and a breakpoint is set anywhere

2019-04-19 Thread daniel hahler
daniel hahler added the comment: I think this issue itself might be fixed already / changed since 3.5. I've came up with something similar in this area though, which is only triggered when using Ctrl-C while pdb is waiting for the next statement: https://github.com/python/cpython/pull/12880

[issue14788] Pdb debugs itself after ^C and a breakpoint is set anywhere

2019-03-15 Thread Mark Lawrence
Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14788] Pdb debugs itself after ^C and a breakpoint is set anywhere

2014-07-04 Thread Mark Lawrence
Mark Lawrence added the comment: A quick glance tells me the patch is okay, apart from the name test_issue_XXX, so can we have a formal patch review please. See also #14743. -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.2 ___

[issue14788] Pdb debugs itself after ^C and a breakpoint is set anywhere

2012-05-18 Thread Terry J. Reedy
Changes by Terry J. Reedy tjre...@udel.edu: -- nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14788 ___ ___ Python-bugs-list

[issue14788] Pdb debugs itself after ^C and a breakpoint is set anywhere

2012-05-12 Thread Xavier de Gaye
New submission from Xavier de Gaye xdeg...@gmail.com: When a breakpoint is set anywhere (in which case the global system's trace function is set), interrupting the debuggee causes Pdb to stop into its own code. See the following pdb session run with python on the current head of the default