-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
bdb.Bdb.set_trace: should set f_trace_lines = True #80675
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
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). |
The patch needs a test. |
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? |
Fixed. |
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:
bugs.python.org fields:
Linked PRs
f_trace_lines = True
on all frames uponpdb.set_trace()
#110881The text was updated successfully, but these errors were encountered: