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
Test failure on macOS Sonoma #2540
Comments
Thanks for reporting this @fxcoudert . The assert msg is saying that, we expect an invalid alignment to result in failed allocation, which didn't seem to happen. Could you help to check the things below:
|
For the failure at The test is correctly linked against jemalloc:
But I am not sure if jemalloc's version is indeed called. How would I check that? Is there a way to get log output? |
To enable logging, you will need to configure with
the beginning of the output should look like this (note that the alignments are the invalid ones used in the test):
So p is NULL as expected, but somehow the errno wasn't set. It's supposed to go down this path: Line 2671 in 72cfdce
with a stack trace like this:
|
I see some calls to jemalloc's aligned_alloc() but not all I think: https://gist.github.com/fxcoudert/148e24b15ad0578e1a11ea235c1b6235 In particular, the ones that fail do not appear to go through jemalloc (unless the logging is badly out-of-sync w.r.t. normal stdout/stderr), if I read the output right. |
@fxcoudert it looks all the invalid ones are not going through jemalloc; I wonder if the new compiler is more aware of the syntax and optimized things away? Can you try adding |
I have reduced the test to:
Compiled at
but at |
Reduced:
And another variant:
I think that is invalid behaviour from the compiler. |
Reported to Apple as FB13209585. |
Hi,
jemalloc 5.3.0 builds on macOS Sonoma (release candidate), but it has a test failure on both Intel and ARM on this macOS version (which we did not see in earlier versions).
I would be happy to provide help and debug, given some indications of what to do.
The text was updated successfully, but these errors were encountered: