issue13183 - Fix pdb skipping frames after hitting a breakpoint and running step. Patch by Xavier de Gaye
This commit is contained in:
parent
2e20968feb
commit
42d7081806
13
Lib/bdb.py
13
Lib/bdb.py
|
@ -22,6 +22,7 @@ class Bdb:
|
|||
self.skip = set(skip) if skip else None
|
||||
self.breaks = {}
|
||||
self.fncache = {}
|
||||
self.frame_returning = None
|
||||
|
||||
def canonic(self, filename):
|
||||
if filename == "<" + filename[1:-1] + ">":
|
||||
|
@ -80,7 +81,11 @@ class Bdb:
|
|||
|
||||
def dispatch_return(self, frame, arg):
|
||||
if self.stop_here(frame) or frame == self.returnframe:
|
||||
try:
|
||||
self.frame_returning = frame
|
||||
self.user_return(frame, arg)
|
||||
finally:
|
||||
self.frame_returning = None
|
||||
if self.quitting: raise BdbQuit
|
||||
return self.trace_dispatch
|
||||
|
||||
|
@ -186,6 +191,14 @@ class Bdb:
|
|||
|
||||
def set_step(self):
|
||||
"""Stop after one line of code."""
|
||||
# Issue #13183: pdb skips frames after hitting a breakpoint and running
|
||||
# step commands.
|
||||
# Restore the trace function in the caller (that may not have been set
|
||||
# for performance reasons) when returning from the current frame.
|
||||
if self.frame_returning:
|
||||
caller_frame = self.frame_returning.f_back
|
||||
if caller_frame and not caller_frame.f_trace:
|
||||
caller_frame.f_trace = self.trace_dispatch
|
||||
self._set_stopinfo(None, None)
|
||||
|
||||
def set_next(self, frame):
|
||||
|
|
|
@ -5,6 +5,7 @@ import pdb
|
|||
import sys
|
||||
import unittest
|
||||
import subprocess
|
||||
import textwrap
|
||||
|
||||
from test import support
|
||||
# This little helper class is essential for testing pdb under doctest.
|
||||
|
@ -595,6 +596,22 @@ def test_pdb_run_with_code_object():
|
|||
|
||||
class PdbTestCase(unittest.TestCase):
|
||||
|
||||
def run_pdb(self, script, commands):
|
||||
"""Run 'script' lines with pdb and the pdb 'commands'."""
|
||||
filename = 'main.py'
|
||||
with open(filename, 'w') as f:
|
||||
f.write(textwrap.dedent(script))
|
||||
cmd = [sys.executable, '-m', 'pdb', filename]
|
||||
stdout = stderr = None
|
||||
with subprocess.Popen(cmd, stdout=subprocess.PIPE,
|
||||
stdin=subprocess.PIPE,
|
||||
stderr=subprocess.STDOUT,
|
||||
) as proc:
|
||||
stdout, stderr = proc.communicate(str.encode(commands))
|
||||
stdout = stdout and bytes.decode(stdout)
|
||||
stderr = stderr and bytes.decode(stderr)
|
||||
return stdout, stderr
|
||||
|
||||
def test_issue7964(self):
|
||||
# open the file as binary so we can force \r\n newline
|
||||
with open(support.TESTFN, 'wb') as f:
|
||||
|
@ -610,6 +627,40 @@ class PdbTestCase(unittest.TestCase):
|
|||
self.assertNotIn(b'SyntaxError', stdout,
|
||||
"Got a syntax error running test script under PDB")
|
||||
|
||||
def test_issue13183(self):
|
||||
script = """
|
||||
from bar import bar
|
||||
|
||||
def foo():
|
||||
bar()
|
||||
|
||||
def nope():
|
||||
pass
|
||||
|
||||
def foobar():
|
||||
foo()
|
||||
nope()
|
||||
|
||||
foobar()
|
||||
"""
|
||||
commands = """
|
||||
from bar import bar
|
||||
break bar
|
||||
continue
|
||||
step
|
||||
step
|
||||
quit
|
||||
"""
|
||||
bar = """
|
||||
def bar():
|
||||
print('1')
|
||||
"""
|
||||
with open('bar.py', 'w') as f:
|
||||
f.write(textwrap.dedent(bar))
|
||||
stdout, stderr = self.run_pdb(script, commands)
|
||||
self.assertIn('main.py(5)foo()->None', stdout.split('\n')[-3],
|
||||
'Fail to step into the caller after a return')
|
||||
|
||||
def tearDown(self):
|
||||
support.unlink(support.TESTFN)
|
||||
|
||||
|
|
|
@ -59,6 +59,9 @@ Core and Builtins
|
|||
Library
|
||||
-------
|
||||
|
||||
- Issue #13183: Fix pdb skipping frames after hitting a breakpoint and running
|
||||
step. Patch by Xavier de Gaye.
|
||||
|
||||
- Issue #14696: Fix parser module to understand 'nonlocal' declarations.
|
||||
|
||||
- Issue #10941: Fix imaplib.Internaldate2tuple to produce correct result near
|
||||
|
|
Loading…
Reference in New Issue