-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
gh-58933: Make pdb return to caller frame correctly when f_trace is not set #118979
Conversation
Hi @iritkatriel , this is a bug fix (a rather important one I think) and maybe it should be backported? |
Thanks @gaogaotiantian for the PR, and @iritkatriel for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
Sorry, @gaogaotiantian and @iritkatriel, I could not cleanly backport this to
|
As |
And I'll work on the cherry pick. |
Thanks @gaogaotiantian for the PR, and @iritkatriel for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
…e is not set (pythonGH-118979) (cherry picked from commit f526314) Co-authored-by: Tian Gao <gaogaotiantian@hotmail.com>
GH-119007 is a backport of this pull request to the 3.13 branch. |
GH-119008 is a backport of this pull request to the 3.12 branch. |
For commands like
next
,return
,until
on a return event, iff_trace
of the previous frame is not set, the command will not stop at the previous frame. A similar issue is fixed forstep
, we are generalizing that fix to commands other thancontinue
.