-
-
Notifications
You must be signed in to change notification settings - Fork 34.7k
[3.7] bpo-17288: Prevent jumps from 'return' and 'exception' trace events #5928
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
eee0041
bpo-17288: Prevent jumps from 'return' and 'exception' trace events
xdegaye 69c1bcb
The new tests use now the jump_test() decorator
xdegaye 8cadc6e
JumpTestCase line numbers are relative to the first line of the testi…
xdegaye a6ec0e0
Restore previous comments
xdegaye File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 change: 1 addition & 0 deletions
1
Misc/NEWS.d/next/Core and Builtins/2018-02-27-13-36-21.bpo-17288.Gdj24S.rst
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| Prevent jumps from 'return' and 'exception' trace events. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a need to check for RETURN_VALUE as in your original patch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only function called by
_PyEval_EvalFrameDefault()that may allow a jump to another line ismaybe_call_line_trace()becausestack_pointeris saved onf->f_stacktopbefore the call and there is aJUMPTO(f->f_lasti)after the call. All the other trace functions called within_PyEval_EvalFrameDefault()are called withf->f_stacktop == NULLexcept after the handling of theYIELD_FROMandYIELD_VALUEopcodes. So by forbidding jumps inframe_setlineno()whenf->f_stacktop == NULLwe handle all the cases, including theRETURN_VALUEopcode, except the yield statements. The check forRETURN_VALUEin my original patch was overkill.