This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Pdb debugs itself after ^C and a breakpoint is set anywhere
Type: behavior Stage:
Components: Library (Lib) Versions: Python 3.4, Python 3.5
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: blueyed, georg.brandl, xdegaye
Priority: normal Keywords: patch

Created on 2012-05-12 10:07 by xdegaye, last changed 2022-04-11 14:57 by admin.

File name Uploaded Description Edit
pdb_default.patch xdegaye, 2012-05-12 10:07 review
Messages (3)
msg160467 - (view) Author: Xavier de Gaye (xdegaye) * (Python triager) Date: 2012-05-12 10:07
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 branch from the repo.

===   =================================
import time
def bar():
    i = 1
    while i:

$ python -m pdb
> /path_to/<module>()
-> import time
(Pdb) import sys; print(sys.version)
3.3.0a3+ (default:4e9680570be8, May 11 2012, 12:09:15) 
[GCC 4.3.2]
(Pdb) break bar
Breakpoint 1 at /path_to/
(Pdb) continue
> /path_to/
-> i = 1
(Pdb) continue
Program interrupted. (Use 'cont' to resume).
> /home/xavier/src/cpython/cpython-hg-default/Lib/
-> def set_trace(self, frame=None):
(Pdb) where
-> exec(cmd, globals, locals)
-> bar()
-> time.sleep(.100)
-> self.set_trace(frame)
> /home/xavier/src/cpython/cpython-hg-default/Lib/
-> def set_trace(self, frame=None):
(Pdb) quit

The attached patch fixes the problem and includes a test case. This
fix is the same as the one proposed at issue 14743 to fix another
problem, except that the set_step call is moved at the end of the
sigint_handler method for the sake of robustness.
msg222267 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2014-07-04 07:35
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.
msg340536 - (view) Author: daniel hahler (blueyed) * Date: 2019-04-19 10:51
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:
Date User Action Args
2022-04-11 14:57:30adminsetgithub: 58993
2019-04-19 10:51:51blueyedsetnosy: + blueyed
messages: + msg340536
2019-03-16 00:13:36BreamoreBoysetnosy: - BreamoreBoy
2014-07-04 07:35:49BreamoreBoysetnosy: + BreamoreBoy

messages: + msg222267
versions: + Python 3.4, Python 3.5, - Python 3.2
2012-05-18 17:47:23terry.reedysetnosy: + georg.brandl
2012-05-12 10:07:36xdegayecreate