bdb.Bdb.set_trace: should set f_trace_lines = True

[blueyed]

BPO	36494
Nosy	@blueyed, @iritkatriel
PRs	bpo-36494: bdb.Bdb.set_trace: set frame.f_trace_lines = True #12640

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2019-03-31.14:28:51.712>
labels = ['type-bug', 'library', '3.9', '3.10', '3.11']
title = 'bdb.Bdb.set_trace: should set f_trace_lines = True'
updated_at = <Date 2021-05-21.21:16:24.081>
user = 'https://github.com/blueyed'

bugs.python.org fields:

activity = <Date 2021-05-21.21:16:24.081>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-03-31.14:28:51.712>
creator = 'blueyed'
dependencies = []
files = []
hgrepos = []
issue_num = 36494
keywords = ['patch']
message_count = 2.0
messages = ['339259', '394158']
nosy_count = 2.0
nosy_names = ['blueyed', 'iritkatriel']
pr_nums = ['12640']
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue36494'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

Linked PRs

• gh-80675: Set f_trace_lines = True on all frames upon pdb.set_trace() #110881

[blueyed]

bdb.Bdb.set_trace should set "f_trace_lines = True" on frames explicitly.

Otherwise they might be skipped if something else has set it to False already, e.g. via a suggested change for coverage.py to set this for performance reasons (nedbat/coveragepy#791).

[iritkatriel]

The patch needs a test.

[nedbat]

Coverage.py now sets f_trace_lines=0 when it doesn't want to trace, and I've started getting bug reports that this breaks tests using pdb: nedbat/coveragepy#1402. Can we move this forward?

[iritkatriel]

@nedbat, I don't think @blueyed plans to finish this. Would you like to take over?

[gaogaotiantian]

Fixed.