search for: asan_symbolize

.../opt/rh/llvm-toolset-7/root/usr/bin/llvm-symbolizer --version LLVM (http://llvm.org/): LLVM version 5.0.1 Optimized build. Default target: x86_64-unknown-linux-gnu Host CPU: nocona I am getting the following error (The addr2line is working ok, also gdb is able to parse these files): python asan_symbolize.py < asan.log.173664 ================================================================= ==173664== ERROR: AddressSanitizer: heap-use-after-free on address 0x60040002ff90 at pc 0x7f83d22f91bb bp 0x7f83c17f3e40 sp 0x7f83c17f3e30 WRITE of size 4 at 0x60040002ff90 thread T12 #0 0x7f83d22f91ba (/...

...thoughts on this RFC on the patch would be appreciated. # Issues with the existing solutions * An official parser for sanitizer reports does not exist. Currently we just tell our users to implement their own (e.g. [1]). This creates an unnecessary duplication of effort. * The existing symbolizer (asan_symbolize.py) only works with ASan reports and doesn’t support other sanitizers like TSan. * The architecture of the existing symbolizer makes it cumbersome to support inline frames. * The architecture of the existing symbolizer is sequential which prevents performing batched symbolication of stack frames....

...'thread' are failing for me this morning. How are your bots looking? Last good commit here was 512c616cacf70ca029a2bf719a482b902f3687cd. > You could try preprocessing your report with perl or sed to fix paths > to your binaries. It would be great to have an option for that in > asan_symbolize.py. > > As for addr2line, we just install binutils-multiarch ubuntu package. Cool, that gets the job done, thanks. Looks like there's some effort going into embedding the addr2line functionality into compiler-rt. Is that something folks are actively working on? > Tests are differe...

...so we can demangle the output adb pull /system/lib/libc.so out/ adb pull /data/data/libclang_rt.asan-arm-android.so out/ # Fix-up the output and demangle sed 's/\/data\/data/out/g' out/err.txt | \ sed 's/\/system\/lib/out/g' | \ $LLVM_DIR/utils/sanitizers/asan_symbolize.py --demangle Is it possible to embed llvm-symbolizer into the ASan runtime? Thanks, Greg

...was > 512c616cacf70ca029a2bf719a482b902f3687cd. > Hm, our bots seem to be green. Could you refer to guilty svn revision? > > > You could try preprocessing your report with perl or sed to fix paths > > to your binaries. It would be great to have an option for that in > > asan_symbolize.py. > > > > As for addr2line, we just install binutils-multiarch ubuntu package. > > Cool, that gets the job done, thanks. Looks like there's some effort > going into embedding the addr2line functionality into compiler-rt. Is > that something folks are actively working...

...2/projects/compiler-rt/lib/asan/lit_tests/Output/deep_thread_stack.cc.tmp && /local/mnt/workspace/draco/out/release_stage2/projects/compiler-rt/lib/asan/lit_tests/Output/deep_thread_stack.cc.tmp 2>&1 | /local/mnt/workspace/draco/compiler-rt/lib/asan/lit_tests/../lit_tests/../scripts/asan_symbolize.py | c++filt | FileCheck /local/mnt/workspace/draco/compiler-rt/lib/asan/lit_tests/deep_thread_stack.cc /local/mnt/workspace/draco/out/release_stage2/bin/clang -ccc-cxx -fsanitize=address -mno-omit-leaf-frame-pointer -fno-omit-frame-pointer -fno-optimize-sibling-calls -g -m64 -O1 /local/mnt/workspa...

...id, I built the ASan shared object and successfully ran this example: https://code.google.com/p/address-sanitizer/source/browse/wiki/example_UseAfterFree.cc?r=1580 But unlike these instructions: http://www.chromium.org/developers/testing/addresssanitizer the Android instructions don't mention asan_symbolize.py https://code.google.com/p/address-sanitizer/wiki/Android When I use asan_symbolize.py (from Linux), I see no symbols in the stack trace and the following error messages: addr2line: '/data/example_UseAfterFree': No such file addr2line: '/data/libclang_rt.asan-arm-android.so': N...

...successfully ran this > example: > > https://code.google.com/p/address-sanitizer/source/browse/wiki/example_UseAfterFree.cc?r=1580 > > But unlike these instructions: > http://www.chromium.org/developers/testing/addresssanitizer > > the Android instructions don't mention asan_symbolize.py > https://code.google.com/p/address-sanitizer/wiki/Android > > When I use asan_symbolize.py (from Linux), I see no symbols in the stack > trace and the following error messages: > > addr2line: '/data/example_UseAfterFree': No such file > addr2line: '/data/libcla...

...; adb pull /system/lib/libc.so out/ > adb pull /data/data/libclang_rt.asan-arm-android.so out/ > > # Fix-up the output and demangle > sed 's/\/data\/data/out/g' out/err.txt | \ > sed 's/\/system\/lib/out/g' | \ > $LLVM_DIR/utils/sanitizers/asan_symbolize.py --demangle > > Is it possible to embed llvm-symbolizer into the ASan runtime? > We have a working solution for using in-process symbolization in sanitizer tools (for Linux/x86_64), but it's somewhat complicated and is not yet upstreamed. Once it's in the trunk, it should be pos...

...gt; >> # Issues with the existing solutions >> >> * An official parser for sanitizer reports does not exist. Currently >> we just tell our users to implement their own (e.g. [1]). This creates >> an unnecessary duplication of effort. >> * The existing symbolizer (asan_symbolize.py) only works with ASan >> reports and doesn’t support other sanitizers like TSan. >> * The architecture of the existing symbolizer makes it cumbersome to >> support inline frames. >> * The architecture of the existing symbolizer is sequential which >> prevents perfor...

...lib/libc.so out/ >> adb pull /data/data/libclang_rt.asan-arm-android.so out/ >> >> # Fix-up the output and demangle >> sed 's/\/data\/data/out/g' out/err.txt | \ >> sed 's/\/system\/lib/out/g' | \ >> $LLVM_DIR/utils/sanitizers/asan_symbolize.py --demangle >> >> Is it possible to embed llvm-symbolizer into the ASan runtime? > > > We have a working solution for using in-process symbolization in sanitizer > tools > (for Linux/x86_64), but it's somewhat complicated and is not yet upstreamed. > Once it'...

...r-rt/lib/asan/lit_tests/Output/stack-overflow.cc.tmp && /sw/src/fink.build/llvm32-3.2-0/llvm-3.2/build/projects/compiler-rt/lib/asan/lit_tests/Output/stack-overflow.cc.tmp 2>&1 | /sw/src/fink.build/llvm32-3.2-0/llvm-3.2/projects/compiler-rt/lib/asan/lit_tests/../lit_tests/../scripts/asan_symbolize.py | c++filt | FileCheck /sw/src/fink.build/llvm32-3.2-0/llvm-3.2/projects/compiler-rt/lib/asan/lit_tests/stack-overflow.cc etc. Is this occuring on linux as well? Jack

...sts/Output/stack-overflow.cc.tmp > && > /sw/src/fink.build/llvm32-3.2-0/llvm-3.2/build/projects/compiler-rt/lib/asan/lit_tests/Output/stack-overflow.cc.tmp > 2>&1 | > /sw/src/fink.build/llvm32-3.2-0/llvm-3.2/projects/compiler-rt/lib/asan/lit_tests/../lit_tests/../scripts/asan_symbolize.py > | c++filt | FileCheck > /sw/src/fink.build/llvm32-3.2-0/llvm-3.2/projects/compiler-rt/lib/asan/lit_tests/stack-overflow.cc > > etc. Is this occuring on linux as well? > Jack > _______________________________________________ > LLVM Developers mailing list >...

...-overflow.cc.tmp >> && >> /sw/src/fink.build/llvm32-3.2-0/llvm-3.2/build/projects/compiler-rt/lib/asan/lit_tests/Output/stack-overflow.cc.tmp >> 2>&1 | >> /sw/src/fink.build/llvm32-3.2-0/llvm-3.2/projects/compiler-rt/lib/asan/lit_tests/../lit_tests/../scripts/asan_symbolize.py >> | c++filt | FileCheck >> /sw/src/fink.build/llvm32-3.2-0/llvm-3.2/projects/compiler-rt/lib/asan/lit_tests/stack-overflow.cc >> >> etc. Is this occuring on linux as well? >> Jack >> _______________________________________________ >> LLVM D...

On Wed, May 29, 2013 at 5:40 PM, Greg Fitzgerald <garious at gmail.com> wrote: > For me, UBsan fails with clang 3.2 and passes with clang 3.3. > Cool, can you use clang 3.3 then? :) I think that the reason selected UBSan tests fail under clang 3.2 is a bug in Clang, which was fixed (Richard may correct me if I'm wrong). I don't really want to mark these tests as "failing

For me, UBsan fails with clang 3.2 and passes with clang 3.3. Using a fixed version allows you to build all clang/llvm/compiler-rt with one compiler. It simplifies the build process quite a bit. Also better for isolating regressions in compiler-rt, especially if you use git-bisect. Greg On May 29, 2013, at 12:30 AM, Alexey Samsonov <samsonov at google.com> wrote: > UBsan tests work