Skip to content
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

Address sanitizer sometimes fails at launch #5156

Open
kimden opened this issue Aug 14, 2024 · 0 comments
Open

Address sanitizer sometimes fails at launch #5156

kimden opened this issue Aug 14, 2024 · 0 comments

Comments

@kimden
Copy link
Contributor

kimden commented Aug 14, 2024

Executables compiled with -DUSE_ASAN=ON, regardless of CMake build type (Debug, RelWithDebInfo, or Release), can fail with the following log (there are no other lines):

AddressSanitizer:DEADLYSIGNAL
AddressSanitizer:DEADLYSIGNAL
AddressSanitizer:DEADLYSIGNAL
AddressSanitizer:DEADLYSIGNAL
AddressSanitizer:DEADLYSIGNAL
AddressSanitizer:DEADLYSIGNAL
Segmentation fault (core dumped)

In that case, backtrace seems pretty useless even in Debug:

(gdb) bt
#0  0x000071f4c68bcf1f in ?? ()
#1  0x0000000000000000 in ?? ()

I ran six different versions (server and client in three build types), 1000 times each, for all of them I have 24-27% of runs failed with that log. The rest started running normally.

Running bots also fails like that sometimes, though I haven't checked it much. I'm not yet aware of what could cause that probability, or any other things that could help this being reproducible.

Steps to reproduce

  1. Compile STK with cmake .. -DCMAKE_BUILD_TYPE=Debug -DNO_SHADERC=OFF -DUSE_ASAN=ON, or any other CMAKE_BUILD_TYPE
  2. Run it, with around 25% probability the log above should appear.

Configuration

STK release version: latest git 9f1b54d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants