Displaying 3 results from an estimated 3 matches for "__asan_stack_malloc_2".
Did you mean:
__asan_stack_malloc_0
2014 Nov 02
2
[LLVMdev] So I just did a normal 'ninja check' with a CMake build that enables ASan and the go bindings tests are... busted...
Specifically, the test is causing a link to occur for CGO stuff. It has
been running 8 minutes now with Gold, and is producing a 400mb .o file
afaict:
% du -hs /tmp/go-build703430446/
llvm.org/llvm/bindings/go/llvm/_test/_obj_test/_cgo_.o
397M /tmp/go-build703430446/
llvm.org/llvm/bindings/go/llvm/_test/_obj_test/_cgo_.o
What am I doing wrong here?
-------------- next part --------------
An
2020 Oct 22
0
[cfe-dev] AddressSanitizer
...>> reference to `__asan_set_shadow_f8'
>>> /usr/bin/ld: /home/bryanpkc/llvm-project/build/lib/libomp.so: undefined
>>> reference to `__asan_stack_malloc_8'
>>> /usr/bin/ld: /home/bryanpkc/llvm-project/build/lib/libomp.so: undefined
>>> reference to `__asan_stack_malloc_2'
>>> /usr/bin/ld: /home/bryanpkc/llvm-project/build/lib/libomp.so: undefined
>>> reference to `__asan_unregister_globals'
>>>
>>> This type of failures are affecting multiple groups of tests:
>>>
>>> Builtins-aarch64-linux :: *
>>&...
2020 Oct 20
4
AddressSanitizer
Hi lists,
I am encountering a large number of check-clang failures after building
Clang/LLVM with -DLLVM_USE_SANITIZER=Address. I have reported the issue on
Bugzilla (https://bugs.llvm.org/show_bug.cgi?id=47678). I cannot even
compile helloworld.c with the resulting clang tool without a lot of false
positives from ASan. Is it because I am not supposed to use GCC's
AddressSanitizer when