-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
ASAN: AddressSanitizer CHECK failed: ((m)) != (0)" (0x0, 0x0) #1193
Comments
…ers#1193 Summary: add debug code to chase down a rare crash in asan/lsan google/sanitizers#1193 Reviewers: vitalybuka Subscribers: #sanitizers, llvm-commits Tags: #sanitizers Differential Revision: https://reviews.llvm.org/D80967
…ers#1193 Summary: add debug code to chase down a rare crash in asan/lsan google/sanitizers#1193 Reviewers: vitalybuka Subscribers: #sanitizers, llvm-commits Tags: #sanitizers Differential Revision: https://reviews.llvm.org/D80967
…t being able to reproduce it for a few months, but the users are seeing it) mode debug code Reviewed By: vitalybuka Differential Revision: https://reviews.llvm.org/D84819
…t being able to reproduce it for a few months, but the users are seeing it) mode debug code Reviewed By: vitalybuka Differential Revision: https://reviews.llvm.org/D84819
I just got this with a note to update this issue: sponge2/c301a9e8-8839-4215-b0aa-b01c99883e93 |
Thanks, I'll take a look. |
Reproducer
|
|
Used for google/sanitizers#1193 Reviewed By: morehouse Differential Revision: https://reviews.llvm.org/D86933
…t being able to reproduce it for a few months, but the users are seeing it) mode debug code Reviewed By: vitalybuka Differential Revision: https://reviews.llvm.org/D84819
Fixes google/sanitizers#1193. AsanChunk can be uninitialized yet just after return from the secondary allocator. If lsan starts scan just before metadata assignment it can fail to find corresponding AsanChunk. It should be safe to ignore this and let lsan to assume that AsanChunk is in the beginning of the block. This block is from the secondary allocator and created with mmap, so it should not contain any pointers and will make lsan to miss some leaks. Similar already happens for primary allocator. If it can't find real AsanChunk it falls back and assume that block starts with AsanChunk. Then if the block is already returned to allocator we have garbage in AsanChunk and may scan dead memory hiding some leaks. I'll fix this in D87135. Reviewed By: morehouse Differential Revision: https://reviews.llvm.org/D86931
Used for google/sanitizers#1193 Reviewed By: morehouse Differential Revision: https://reviews.llvm.org/D86933
…t being able to reproduce it for a few months, but the users are seeing it) mode debug code Reviewed By: vitalybuka Differential Revision: https://reviews.llvm.org/D84819
Fixes google/sanitizers#1193. AsanChunk can be uninitialized yet just after return from the secondary allocator. If lsan starts scan just before metadata assignment it can fail to find corresponding AsanChunk. It should be safe to ignore this and let lsan to assume that AsanChunk is in the beginning of the block. This block is from the secondary allocator and created with mmap, so it should not contain any pointers and will make lsan to miss some leaks. Similar already happens for primary allocator. If it can't find real AsanChunk it falls back and assume that block starts with AsanChunk. Then if the block is already returned to allocator we have garbage in AsanChunk and may scan dead memory hiding some leaks. I'll fix this in D87135. Reviewed By: morehouse Differential Revision: https://reviews.llvm.org/D86931
Used for google/sanitizers#1193 Reviewed By: morehouse Differential Revision: https://reviews.llvm.org/D86933
…t being able to reproduce it for a few months, but the users are seeing it) mode debug code Reviewed By: vitalybuka Differential Revision: https://reviews.llvm.org/D84819
Very rarely we've seen this CHECK failed in asan allocator
There is no known reproducer yet.
==4979==AddressSanitizer CHECK failed: llvm-project/compiler-rt/lib/asan/asan_allocator.cpp:1042 "((m)) != (0)" (0x0, 0x0)
Tracer caught signal 11: addr=0x8 pc=0x7f524740f420 sp=0x7f5235268160
==4971==LeakSanitizer has encountered a fatal error.
==4971==HINT: For debugging, try setting environment variable LSAN_OPTIONS=verbosity=1:log_threads=1
==4971==HINT: LeakSanitizer does not work under ptrace (strace, gdb, etc)
E0206 05:42:07.026651 4971 allocator.cc:232] RAW:
Internal Google bug: http://b/149237057
The text was updated successfully, but these errors were encountered: