-
Notifications
You must be signed in to change notification settings - Fork 79
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
Tons of uninitialized memory access bugs #199
Comments
When built with -g -fno-inline to get more accurate logs, it straight up segfaults.
|
Can you provide an example file that produces this problem? |
You mean it doesn't blow up for you? That many locations should effect other targets than just rsp. Sec, will grab a test file. |
Seeing if github upload works. |
Nope, doesn't work. Uploaded to https://anonymousfiles.io/m1Rl3kid/ |
I've had no issues with it on Windows with VS 2017 using both debug and release configurations. On Ubuntu 20.04 with GCC 9 it also ran fine, though Valgrind showed some of the same uninitialized value warnings. ASan had no complaints though. What are your build settings? |
gcc 10.2, -O3 -march=nocona -mtune=k8 -fomit-frame-pointer |
Okay, I could reproduce the crash with GCC 9 as well when using -O3 and -fno-inline (Clang 10 works). It seems to crash whenever tinyformat is used at all. Not sure what would cause it though... |
There seem to be newer tinyformat versions, but it appears the copy here is modified to be wchar. It could also be a bug in tinyformat, even the new versions, of course. Just a note, asan catches a small fraction of the stuff valgrind does, I believe even their own docs say so. It's meant to be fast, not complete. |
I was getting corrupted output randomly, and decided to run armips under valgrind. It blew up in over 20 places:
The text was updated successfully, but these errors were encountered: