-
Notifications
You must be signed in to change notification settings - Fork 29
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
segfault when passing the wrong type to translate
#231
Labels
Comments
jimy-byerley
added a commit
to jimy-byerley/PyGLM
that referenced
this issue
Apr 21, 2024
Merged
Hi Jimy, thank you for reporting this! If I find any additional ones, I'll fix them in your PR. Cheers |
I've looked through the code and found that the only occurence of this error is calling |
Merged
Zuzu-Typ
changed the title
segfault when passing the wrong type to
segfault when passing the wrong type to Apr 21, 2024
translate
or rotate
translate
Zuzu-Typ
added a commit
that referenced
this issue
Apr 21, 2024
Thanks for answering so fast :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello @Zuzu-Typ
I have a systematic segfault when passing some wrong type to
translate
androtate
right argument types work well, but any argument that should theoretically raise a
TypeError
triggers a segfaultIt seems to come from this macro according to
gdb
I seems to be due to when
arg2
is NULL, this macro still attempts to retreive its type name.So I fixed it by introducing
and calling
PyGLM_TYPEERROR_1O
when onlyarg1
is non-nulland calling
PyGLM_TYPEERROR_2O
when botharg1
andarg2
are non-nullThe text was updated successfully, but these errors were encountered: