search for: asan_interface_test

...inja check-all FAILED: cd [..]bld/projects/compiler-rt/lib/asan/tests && [...]/bld/./bin/clang ASAN_INST_TEST_OBJECTS.gtest-all.cc.i386-with-calls.o ASAN_INST_TEST_OBJECTS.asan_asm_test.cc.i386-with-calls.o ASAN_INST_TEST_OBJECTS.asan_globals_test.cc.i386-with-calls.o ASAN_INST_TEST_OBJECTS.asan_interface_test.cc.i386-with-calls.o ASAN_INST_TEST_OBJECTS.asan_test.cc.i386-with-calls.o ASAN_INST_TEST_OBJECTS.asan_oob_test.cc.i386-with-calls.o ASAN_INST_TEST_OBJECTS.asan_mem_test.cc.i386-with-calls.o ASAN_INST_TEST_OBJECTS.asan_str_test.cc.i386-with-calls.o ASAN_INST_TEST_OBJECTS.asan_test_main.cc.i386-with...

Hi, I'm trying to run the ASAN tests on ARM (to fix the CMake RT bot we have) and I'm hitting a different bug on my Chomebook than I have on the bots: [6/32] Generating ASAN_INST_TEST_OBJECTS.asan_interface_test.cc.arm-inline.o ... clang-3.6: warning: argument unused during compilation: '-march=armv7-a' clang (LLVM option parsing): Unknown command line argument '-asan-instrument-assembly'. clang (LLVM option parsing): Did you mean '-asan-instrument-atomics'? Is that option unavaila...

...D: cd [..]bld/projects/compiler-rt/lib/asan/tests && > [...]/bld/./bin/clang ASAN_INST_TEST_OBJECTS.gtest-all.cc.i386-with-calls.o > ASAN_INST_TEST_OBJECTS.asan_asm_test.cc.i386-with-calls.o > ASAN_INST_TEST_OBJECTS.asan_globals_test.cc.i386-with-calls.o > ASAN_INST_TEST_OBJECTS.asan_interface_test.cc.i386-with-calls.o > ASAN_INST_TEST_OBJECTS.asan_test.cc.i386-with-calls.o > ASAN_INST_TEST_OBJECTS.asan_oob_test.cc.i386-with-calls.o > ASAN_INST_TEST_OBJECTS.asan_mem_test.cc.i386-with-calls.o > ASAN_INST_TEST_OBJECTS.asan_str_test.cc.i386-with-calls.o > ASAN_INST_TEST_OBJECTS.as...

...ojects/compiler-rt/lib/asan/tests && >> [...]/bld/./bin/clang ASAN_INST_TEST_OBJECTS.gtest-all.cc.i386-with-calls.o >> ASAN_INST_TEST_OBJECTS.asan_asm_test.cc.i386-with-calls.o >> ASAN_INST_TEST_OBJECTS.asan_globals_test.cc.i386-with-calls.o >> ASAN_INST_TEST_OBJECTS.asan_interface_test.cc.i386-with-calls.o >> ASAN_INST_TEST_OBJECTS.asan_test.cc.i386-with-calls.o >> ASAN_INST_TEST_OBJECTS.asan_oob_test.cc.i386-with-calls.o >> ASAN_INST_TEST_OBJECTS.asan_mem_test.cc.i386-with-calls.o >> ASAN_INST_TEST_OBJECTS.asan_str_test.cc.i386-with-calls.o >> ASAN_...

...tremely helpful to have a very firm separation between bucket #1 and bucket #2. Currently, there is one collection of tests clearly in bucket #1 (asan_noinst_test.cc), and plenty of tests clearly in bucket #2, but there seems to be quite a bit of overlap as well. For example, I would naively expect asan_interface_test.cc to not require instrumentation -- it almost exclusively directly calls the runtime. But it is currently being compiled with instrumentation by the Makefile.old, so I'm at a loss. Separating these two scenarios into at least separate files, and ideally linking them into two separate binaries...

...ering parts at a time) Agree. I am going to fix that now. > Currently, there is one collection of tests clearly in bucket #1 > (asan_noinst_test.cc), and plenty of tests clearly in bucket #2, but there > seems to be quite a bit of overlap as well. For example, I would naively > expect asan_interface_test.cc to not require instrumentation -- it almost > exclusively directly calls the runtime. But it is currently being compiled > with instrumentation by the Makefile.old, so I'm at a loss. Separating > these two scenarios into at least separate files, and ideally linking them > into tw...

...test.cc - Prelinking not supported: compiler-rt/test/asan/TestCases/Linux/asan_prelink_test.cc - Intra-object padding not supported: compiler-rt/test/asan/TestCases/intra-object-overflow.cc - Calls __asan_poison_memory_region in middle of shadow byte: compiler-rt/lib/asan/tests/asan_interface_test.cc SimplePoisonMemoryRegionTest OverlappingPoisonMemoryRegionTest PoisoningStressTest compiler-rt/test/asan/TestCases/small_memcpy_test.cc compiler-rt/test/asan/TestCases/strtol_strict.c compiler-rt/test/asan/TestCases/strtoll_strict.c - Has hardwired memory map:...

...rt/lib/asan/tests && >>> [...]/bld/./bin/clang ASAN_INST_TEST_OBJECTS.gtest-all.cc.i386-with-calls.o >>> ASAN_INST_TEST_OBJECTS.asan_asm_test.cc.i386-with-calls.o >>> ASAN_INST_TEST_OBJECTS.asan_globals_test.cc.i386-with-calls.o >>> ASAN_INST_TEST_OBJECTS.asan_interface_test.cc.i386-with-calls.o >>> ASAN_INST_TEST_OBJECTS.asan_test.cc.i386-with-calls.o >>> ASAN_INST_TEST_OBJECTS.asan_oob_test.cc.i386-with-calls.o >>> ASAN_INST_TEST_OBJECTS.asan_mem_test.cc.i386-with-calls.o >>> ASAN_INST_TEST_OBJECTS.asan_str_test.cc.i386-with-calls....

+ more asan folks, please CC them to the code reviews. Also please make sure llvm-commits is CC-ed (cfe-commits for clang changes) On Tue, Oct 31, 2017 at 2:29 PM, Walter Lee <waltl at google.com> wrote: > I've prepared a preliminary set of patches that makes ASan work with > 32-byte shadow granularity, and I would like to get some feedback on > those patches as well as my

...d by r159135. thanks!! --kcc > > >> Currently, there is one collection of tests clearly in bucket #1 >> (asan_noinst_test.cc), and plenty of tests clearly in bucket #2, but there >> seems to be quite a bit of overlap as well. For example, I would naively >> expect asan_interface_test.cc to not require instrumentation -- it almost >> exclusively directly calls the runtime. But it is currently being compiled >> with instrumentation by the Makefile.old, so I'm at a loss. Separating >> these two scenarios into at least separate files, and ideally linking them...