Fix calling symbol proc from using scope outside
#13230
Open
+12
−1
Conversation
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
Previously, resolve_refined_method() wrote to defined_class_ptr by using rb_method_entry_t::defined_class, which by definition can be 0. Since `*defined_class_ptr` is used as a back-up when rb_method_entry_t::defined_class is 0, this wasn't a good strategy to not have 0 at the end. This caused a crash since it overwrote a properly set defined_class put by a `search_method*` function earlier. Since resolve_refined_method() is always called after calling a `search_method_*` function which writes through defined_class_ptr already, just don't write through deinfed_class_ptr. [Bug #21265]
This comment has been minimized.
This comment has been minimized.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously, resolve_refined_method() wrote to defined_class_ptr by using
rb_method_entry_t::defined_class, which by definition can be 0. Since
*defined_class_ptris used as a back-up whenrb_method_entry_t::defined_class is 0, this wasn't a good strategy to
not have 0 at the end. This caused a crash since it overwrote a properly
set defined_class put by a
search_method*function earlier.Since resolve_refined_method() is always called after calling a
search_method_*function which writes through defined_class_ptr already,just don't write through deinfed_class_ptr.
[Bug #21265]