You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
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
Compile STK with cmake .. -DCMAKE_BUILD_TYPE=Debug -DNO_SHADERC=OFF -DUSE_ASAN=ON, or any other CMAKE_BUILD_TYPE
Run it, with around 25% probability the log above should appear.
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):In that case, backtrace seems pretty useless even in Debug:
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
cmake .. -DCMAKE_BUILD_TYPE=Debug -DNO_SHADERC=OFF -DUSE_ASAN=ON
, or any otherCMAKE_BUILD_TYPE
Configuration
STK release version: latest git 9f1b54d
The text was updated successfully, but these errors were encountered: