Displaying 3 results from an estimated 3 matches for "fast_unwind_on_malloc".
2015 Jan 14
2
[LLVMdev] How do I add suppressions to LSan when testing LLVM with ASan enabled?
I get leaks from a system library:
==16272==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 148 byte(s) in 2 object(s) allocated from:
#0 0x4a3172 in __interceptor_malloc
.../build/../projects/compiler-rt/lib/asan/asan_malloc_linux.cc:40:3
#1 0x7f575d8df1fe in wcsdup (/lib64/libedit.so.0+0x1c1fe)
I don't think I can fix this... ;]
-Chandler
-------------- next part
2014 Oct 08
3
[LLVMdev] More ARM asan failures - Line number
On 7 October 2014 20:55, Evgeniy Stepanov <eugenis at google.com> wrote:
> Can you elaborate on this? Does it ever clean those lines? These
> numbers are correct on multiple other platforms. I wonder if it's some
> codegen peculiarity that leads to this off-by-one mistake? Can you go
> down to the individual compile/run invocation and verify that line
> numbers match (or
2014 Oct 08
2
[LLVMdev] More ARM asan failures - Line number
On 8 October 2014 11:18, Evgeniy Stepanov <eugenis at google.com> wrote:
> Something you could try: ASAN_OPTIONS=fast_unwind_on_malloc=0 should
> switch to cfi unwinder and fix the stack trace, but that's not a
> solution to the problem.
Is this when compiling Clang? The file? or running the final binary?
--renato