-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Bug]: Clang 19 AddressSanitizer crash: terminated by signal SIGSEGV (address boundary error). #21863
Comments
I highly doubt valgrind is working Can you try |
same stuff.
|
After |
|
I think I need Any ideas? @finagolfin @licy183 @sylirre |
The support for aarch64 16kb pagesize in |
I can't reproduce it on my Android 7.x device.
|
I cannot reproduce with your example on Android 13 AArch64, where I regularly run some Swift tests with Asan also. Maybe a specific incompatibility with 8.1 or your device? |
I think that register
|
and
full
this is the source i think, getauxval |
Can you post this with more |
It seems that |
@truboxl what did you mean with up?
something about SELinux. https://stackoverflow.com/questions/51231326/what-is-the-meaning-of-avc-denied-read-for-name-line-in-logcat |
i think maybe from this. |
There is an alternate copy of lib in For |
i think you mean and yes it is working.
about logcat, what do you think i should do? i cant access |
one more thing i think the lib should be implicitly linked.
|
Ah yes sorry about that I suppose something really broke Can you help try |
and logcat pretty much same as before, this is what i do, create new terminal,
no crash dump |
Thanks! This confirms the upcoming NDK r28 will have the same issue. We should report to https://github.com/android/ndk
Yes with the latest log should point to checking Curiously llvm/llvm-project@c6049e6#diff-7aa35d74ad2634ba31a6fede2910e32d837220fd761b6898542d8a0b71ccfe5aL65 mentions |
Problem description
Clang 18 worked just fine, but after upgrading to Clang 19, the executable with Address Sanitizer crashes with signal SIGSEGV.
What steps will reproduce the bug?
echo "int main(){}" | cc -x c -; ./a.out
working just fine.echo "int main(){}" | cc -x c - -fsanitize=address -Wl,-rpath,"/data/data/com.termux/files/usr/lib/clang/19/lib/linux"; ./a.out
crash:'./a.out' terminated by signal SIGSEGV (Address boundary error)
with valgrind
What is the expected behavior?
working just fine.
System information
The text was updated successfully, but these errors were encountered: