Repository navigation
BUG: avoid segfault on bad arguments in ndarray.__array_function__ - #27503
Merged
Merged
Conversation
Member
|
Thanks, Marten! (Not a huge deal, since nobody should call this directly and we sanitize it, but still good to check.) |
Contributor
Author
|
Thanks. Agreed it is hard to hit, but people writing subclasses should still not get segfaults if they do the call wrong. And it is a cheap check. Anyway, happy it is in! |
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
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.
While looking into fixing #27500, I found that one can quite easily cause a core dump:
This is because the arguments to
__array_function__were not checked.Now they are!