[3.14] gh-144446: Fix some frame object thread-safety issues (gh-144479) #144546
+181
−13
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.
Fix thread-safety issues when accessing frame attributes while another
thread is executing the frame:
Add critical section to frame_repr() to prevent races when accessing
the frame's code object and line number
Add _Py_NO_SANITIZE_THREAD to PyUnstable_InterpreterFrame_GetLasti()
to allow intentional racy reads of instr_ptr.
Fix take_ownership() to not write to the original frame's f_executable
(cherry picked from commit 5bb3bbb)
Co-authored-by: Sam Gross colesbury@gmail.com