Uh oh!
There was an error while loading. Please reload this page.
gh-58933: Make pdb return to caller frame correctly when f_trace is not set - #118979
Conversation
gaogaotiantian
commented
May 13, 2024
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 |
gaogaotiantian
commented
May 13, 2024
As |
gaogaotiantian
commented
May 13, 2024
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,untilon a return event, iff_traceof 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.