search for: asan_report

...changed when this happens. This will be enforced with tests. The parsing tools would be subtools of the asan, tsan, ubsan subtools. This would require the user to explicitly communicate the report type ahead of time. Command line invocation would look something like: ``` llvm-xsan asan parse < asan_report.txt > asan_report.json llvm-xsan tsan parse < tsan_report.txt > tsan_report.json llvm-xsan ubsan parse < ubsan_report.txt > ubsan_report.json ``` The structured data format would be JSON. The schema details still need to be worked out but the schema will need to cover every type of...

...>> >> The parsing tools would be subtools of the asan, tsan, ubsan subtools. >> This would require the user to explicitly communicate the report type >> ahead of time. Command line invocation would look something like: >> >> ``` >> llvm-xsan asan parse < asan_report.txt > asan_report.json >> llvm-xsan tsan parse < tsan_report.txt > tsan_report.json >> llvm-xsan ubsan parse < ubsan_report.txt > ubsan_report.json >> ``` >> >> The structured data format would be JSON. The schema details still >> need to be worked...

...rror: no such file or directory: 'libRTSanitizerCommon.test.osx.a' make: *** [/Users/rrelph/llvm/tot/xcode/projects/compiler-rt/lib/sanitizer_common/tests/Sanitizer-i386-Test] Error 1 Command /bin/sh failed with exit code 2 Additionally, there are still the 8 functions declared noreturn in asan_report.cc that clang expects to "not return". These generate 16 warnings during the ALL_BUILD build and 8 more warnings during the check-all build. Richard On Dec 21, 2012, at 12:13 AM, Alexey Samsonov <samsonov at google.com<mailto:samsonov at google.com>> wrote: Hi Richard! On...

...[ DEATH ] WRITE of size 1 at 0x00010cf70e4a thread T16777215 [ DEATH ] 0x00010cf70e4a is located 0 bytes to the right of 10-byte region [0x00010cf70e40,0x00010cf70e4a) [ DEATH ] ==88865== AddressSanitizer CHECK failed: /sw/src/fink.build/llvm32-3.2-0/llvm-3.2/projects/compiler-rt/lib/asan/asan_report.cc:216 "((t)) != (0)" (0x0, 0x0) [ DEATH ] Stats: 0M malloced (0M for red zones) by 2252 calls [ DEATH ] Stats: 0M realloced by 0 calls [ DEATH ] Stats: 0M freed by 1633 calls [ DEATH ] Stats: 0M really freed by 0 calls [ DEATH ] Stats: 4M (1027 full pages) mmaped in 8 call...

Hi Richard! On Thu, Dec 20, 2012 at 12:48 AM, Nick Kledzik <kledzik at apple.com> wrote: > Those look like the linker is being passed the same .o file built twice, > ex: > ../Objects-normal/x86_64/asan_globals_test.o > ../lib/asan/tests/asan_globals_test.cc.asan.o > > So, the symbols are colliding. Something is set up wrong in the xcode > project. > > -Nick