-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
UBSan: runtime undefined behaviours when using -fsanitize=undefined -fno-sanitize-recover
#132097
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
Comments
After the two main PRs (not the cosmetic one) the full test suite should be free of undefined behaviors:
Note that there are still probably undefined behaviors but the paths are not checked at all. For instance, I haven't checked the UBs on the free-threaded build (maybe there are some paths that are affected) or on the JIT. |
I'm going to close this one as it's really completed! we now managed to have a test suite that has no undefined behaviors, both on the regular and free-threaded builds! For the remaining PR that just removes cosmetics, I'll leave it hanging as it's not really pressing and I'm not sure I want to add many cosmetic changes. |
Bug report
Bug description:
We finally managed to fix gh-111178, but this is assuming that Python is compiled with
-fsanitize=function
. When compiling Python as follows (with clang 18.1.8):we still have some tests failing:
Others related to the second item above:
Others on fautlhandler, but I'm not sure whether this is the UB that is being reported or something else:
Finally,
test_regrtest
also fails but the test suite just hangs after crashing (but the UB seems to happen in a test related to XML so it's probably the same thing):CPython versions tested on:
CPython main branch
Operating systems tested on:
Linux
Linked PRs
PyCFunction
and others #131665The text was updated successfully, but these errors were encountered: