search for: asantests

Following a blend of instructions on 3 web pages, I have succeeded in getting LLVM 3.2 (with clang, extras, and compiler-rt) building - but not testing - on Xcode. I used CMake 2.8.10 GUI to create the Xcode project file. Below are my notes. First, I believe CMake ends up setting things up so that Xcode has 1 warning after scanning the project having to do with hires images or some such… it takes

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 On Dec 19, 2012, at 9:48 AM, Relph, Richard wrote: > Following a blend of instructions on 3 web pages, I have succeeded in getting LLVM

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

Different, but still failing (this time with Xcode 4.4…) /Users/rrelph/llvm/tot/xcode/bin/Debug/clang sanitizer_allocator_test.cc.i386.o sanitizer_common_test.cc.i386.o sanitizer_flags_test.cc.i386.o sanitizer_libc_test.cc.i386.o sanitizer_list_test.cc.i386.o sanitizer_printf_test.cc.i386.o sanitizer_stackdepot_test.cc.i386.o sanitizer_test_main.cc.i386.o gtest-all.cc.i386.o

Hi, Jack! On Fri, Nov 2, 2012 at 6:18 PM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > Nick, > Have you noticed that llvm/clang svn produces the following linker > warnings on > 'make check-all'? > > Linking CXX executable Debug/AsanTest > ld: warning: direct access in > llvm::convertible_fwd_ostream::~convertible_fwd_ostream() to global weak >

Nick, Have you noticed that llvm/clang svn produces the following linker warnings on 'make check-all'? Linking CXX executable Debug/AsanTest ld: warning: direct access in llvm::convertible_fwd_ostream::~convertible_fwd_ostream() to global weak symbol vtable for llvm::convertible_fwd_ostream means the weak symbol cannot be overridden at runtime. This was likely caused by different

I'm following these instructions with the latest code from llvm.org: https://code.google.com/p/address-sanitizer/source/browse/trunk/build/scripts/slave/buildbot_cmake.sh Of SanitizerTest, AsanTest and AsanNoinstTest, I cannot get any of the 3 to pass all its tests. I've tried using an Android device running JellyBean as well as the latest Android Emulator (20130917, api level 18).

...its install directory, and the test suite from the CMake build uses the local copy of the ASan runtime for testing. To reproduce the error I'm seeing, run the Android CMake build in the Release+Asserts directory of the Make build. Install the ASan runtime from the Make build and then run the AsanTests test suite. Thanks, Greg On Wed, Oct 16, 2013 at 11:55 PM, Evgeniy Stepanov <eugenis at google.com> wrote: > ARM JellyBean works over here. There is some flakiness in > SanitizerCommon.SpinMutex test. > > > On Wed, Oct 16, 2013 at 11:36 PM, Greg Fitzgerald <garious at gmai...

ARM JellyBean works over here. There is some flakiness in SanitizerCommon.SpinMutex test. On Wed, Oct 16, 2013 at 11:36 PM, Greg Fitzgerald <garious at gmail.com> wrote: > I'm following these instructions with the latest code from llvm.org: > > > https://code.google.com/p/address-sanitizer/source/browse/trunk/build/scripts/slave/buildbot_cmake.sh > > Of

On Fri, Nov 02, 2012 at 06:45:07PM +0400, Alexey Samsonov wrote: > Hi, Jack! > > > I'll take a look at this. However, tests below fail for a different reason > (they don't use Debug/AsanTest at all). > How do you configure a CMake build tree? Can you somehow get (or run > manually) the script which is used > for running log-path_test.cc and other failing test

...and the test suite from the CMake build uses the local copy > of the ASan runtime for testing. > > To reproduce the error I'm seeing, run the Android CMake build in the > Release+Asserts directory of the Make build. Install the ASan runtime > from the Make build and then run the AsanTests test suite. > Do you mean it's a compile-time issue with the path in Android.cmake? > > Thanks, > Greg > > On Wed, Oct 16, 2013 at 11:55 PM, Evgeniy Stepanov <eugenis at google.com> > wrote: > > ARM JellyBean works over here. There is some flakiness in >...

There seems to be a new regression in current llvm/compiler-rt 3.2 branch. On 86_64-apple-darwin12, I am seeing the failure... [100%] Running all regression tests lit.py: lit.common.cfg:19: note: using clang: '/sw/src/fink.build/llvm32-3.2-0/llvm-3.2/build/bin/clang' lit.py: lit.cfg:171: note: using clang: '/sw/src/fink.build/llvm32-3.2-0/llvm-3.2/build/bin/./clang' FAIL:

Context: I'm trying to implement support for ASan's unittest suite in CMake. This is ... quite challenging. I think I can get it to work with one significant caveat: it will require manual dependency management. None of the automatic header tracking. I think this is fine in some cases, and not so fine in other cases. Let me explain. It feels like these tests are really comprised of two