-
Notifications
You must be signed in to change notification settings - Fork 10
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
arm64: AddressSanitizer: container-overflow on address #33
Comments
Yeah I've had that problem it my GitHub Workflow too. GCC and Clang both compile and run fine with sanitizers so I doubt there is anything wrong at all. I'm not sure about that though, so if you'd like to it would help if you could debug it and see if it's actually a bigger issue. Otherwise I'll just assume it's a problem with sanitizer support on Apple Clang (since this issue can occur if parts of the app are instrumented and others are not). |
Hit possibly another sanitizer issue:
Apparently MSVC+Jom cannot link project if different sanitize options were in use, by different submodules. MSVC+Ninja somehow works, not sure why. Suggestion: advice top-level application(OpenGothc) to use global settings instead:
|
It is already possible to disable sanitizer flags in phoenix. You can just |
Tested on mac after switching to global-level sanitizers. Setup in OpenGothic cmake:
Now warning are gone |
Run into this issue, when testing latest OpenGothic build on M1.
Apart from it, game runs fine, if
detect_container_overflow
is disabled. Failure is quite consistent intrigger_list
parse code, yet I wasn't able to spot any suspicius code in relevant places.Full log is below:
0x0002cdc006a0 is located 96 bytes inside of 128-byte region [0x0002cdc00640,0x0002cdc006c0)
allocated by thread T8 here:
Thread T8 created by T0 here:
HINT: if you don't care about these errors you may set ASAN_OPTIONS=detect_container_overflow=0.
If you suspect a false positive see also: https://github.com/google/sanitizers/wiki/AddressSanitizerContainerOverflow.
The text was updated successfully, but these errors were encountered: