search for: addresssanit

Hi, The 6.0.1-rc2 release has been tagged. Testers may begin testing and reporting results. -Tom

Hi, I've just tagged the 6.0.1-rc1 release. Testers may begin testing and uploading binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to do so please try to do this before Friday, because I would like to tag 5.0.2-final then. As a reminder to users and developers, May 18 is the deadline for submitting merge requests for 6.0.1, so there is still time to get bug fixes

...>> >> Please build, test and upload binaries to the sftp. Let me know if >> there are any issues. > > Built and tested rc1. Test failures on amd64-freebsd10: > > FAIL: LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/DummyRPC.TestClearHandlers (1346 of 38616) > FAIL: AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.DoubleFreeTest (2480 of 38616) > FAIL: AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.ReallocFreedPointerTest (2505 of 38616) > FAIL: AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.UseThenFreeThenUseTes...

Dear testers, 5.0.0-rc1 has just been tagged. Please build, test and upload binaries to the sftp. Let me know if there are any issues. I'll upload sources, docs, and your binaries to the pre-release website once they're ready. Thanks, Hans

...e easily fixable, others have been there since a long time, and might be harder to fix. A full overview of the failures on amd64: ******************** Testing Time: 7907.21s ******************** Failing Tests (896): LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/DummyRPC.TestClearHandlers AddressSanitizer-Unit :: ./Asan-i386-calls-Test/AddressSanitizer.DoubleFreeTest AddressSanitizer-Unit :: ./Asan-i386-calls-Test/AddressSanitizer.ReallocFreedPointerTest AddressSanitizer-Unit :: ./Asan-i386-calls-Test/AddressSanitizer.UseThenFreeThenUseTest AddressSanitizer-Unit :: ./Asan-i386-calls-...

On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >>

...uild, test and upload binaries to the sftp. Let me know if >>> there are any issues. >> >> Built and tested rc1. Test failures on amd64-freebsd10: >> >> FAIL: LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/DummyRPC.TestClearHandlers (1346 of 38616) >> FAIL: AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.DoubleFreeTest (2480 of 38616) >> FAIL: AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.ReallocFreedPointerTest (2505 of 38616) >> FAIL: AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.UseThenFreeTh...

Bill, For some reason the llvm-symbolizer tests fail on ppc: http://lab.llvm.org:8011/builders/clang-ppc64le-linux/builds/182/steps/ninja%20check%201/logs/stdio because it can't be started: /home/buildbots/ppc64le-clang-test/clang-ppc64le/stage1/./bin/llvm-symbolizer: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by

...lieve r182853 broke the SanitizerCommon tests and r182854 broke the asan tests, but I'm not 100% certain and unfortunately don't have time to dive into this one. Would you mind taking a quick scan of the logs below and letting me know if anything stands out to you. Failing Tests (14): AddressSanitizer :: Linux/unpoison_tls.cc AddressSanitizer :: deep_thread_stack.cc AddressSanitizer-Unit :: Asan-i386-Test/AddressSanitizer.ManyThreadsTest AddressSanitizer-Unit :: Asan-i386-Test/AddressSanitizer.PthreadExitTest AddressSanitizer-Unit :: Asan-i386-Test/AddressSanitizer.ThreadName...

...I have been working on porting ASan to AArch64. I am building compiler-rt in "standalone mode" targeting aarch64. My build is successful, but I get the following runtime error when I run an ASan enabled executable through qemu-aarch64: ==29184==Parsed ASAN_OPTIONS: verbosity=1 ==29184==AddressSanitizer: failed to intercept '__isoc99_printf' ==29184==AddressSanitizer: failed to intercept '__isoc99_sprintf' ==29184==AddressSanitizer: failed to intercept '__isoc99_snprintf' ==29184==AddressSanitizer: failed to intercept '__isoc99_fprintf' ==29184==AddressSanitizer...

...ct 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...

...to Android, 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: >>...

...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 translation units being compiled with different visibility settings. I am seeing some AddressSanitizer failures like... FAIL: AddressSanitizer :: log-path_test.cc (13 of 12542) ******************** TEST 'AddressSanitizer :: log-path_test.cc' FAILED ******************** FAIL: AddressSanitizer :: strncpy-overflow.cc (27 of 12542) ******************** TEST 'AddressSanitizer :: strncpy...

At 167457 on x86_64-apple-darwin12, I am seeing a slew of AddressSanitizer failures due to unresolved symbols such as... Exit Code: 1 Command Output (stderr): -- Undefined symbols for architecture x86_64: "___asan_init", referenced from: _asan.module_ctor in shared-lib-test-so-moBSTe.o "___asan_register_globals", referenced from: _...

..., Kostya Serebryany <kcc at google.com> wrote: > Hi Reid, > > On Tue, Jun 26, 2012 at 4:30 AM, Reid Watson <reidw at google.com> wrote: > >> Hello, >> >> I'm starting work on a project to detect initialization order problems >> in C++ files using AddressSanitizer. >> The extension in question will hopefully result in AddressSanitizer >> being able to detect initializers which read an undefined value from a >> static or global variable defined in another TU. >> I'm currently working on this as a patch to AddressSanitizer, but...

...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 cases? > > I am seeing some AddressSanitizer failures like... > > FAIL: AddressSanitizer :: log-path_test.cc (13 of 12542) > ******************** TEST 'AddressSanitizer :: log-path_test.cc' FAILED > ******************** > > FAIL: AddressSanitizer :: strncpy-overflow.cc (27 of 12542) > ******************** TEST...

The fix is under review. --kcc On Tue, Nov 6, 2012 at 6:08 AM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > At 167457 on x86_64-apple-darwin12, I am seeing a slew of > AddressSanitizer failures due to > unresolved symbols such as... > > Exit Code: 1 > Command Output (stderr): > -- > Undefined symbols for architecture x86_64: > "___asan_init", referenced from: > _asan.module_ctor in shared-lib-test-so-moBSTe.o > "___asan_regi...

...2012 at 6:18 PM, Kostya Serebryany <kcc at google.com> wrote: > The fix is under review. > > --kcc > > > On Tue, Nov 6, 2012 at 6:08 AM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > >> At 167457 on x86_64-apple-darwin12, I am seeing a slew of >> AddressSanitizer failures due to >> unresolved symbols such as... >> >> Exit Code: 1 >> Command Output (stderr): >> -- >> Undefined symbols for architecture x86_64: >> "___asan_init", referenced from: >> _asan.module_ctor in shared-lib-test-so-mo...

...ild so that we always run the ASan instrumentation test suite for shadow scale values of 3 and 5. - I've gone through the asan test suites to make them run cleanly for both shadow scale=3 and shadow scale=5. Here are the tests I have disabled, grouped by categories: - Instrumentation/AddressSanitizer tests. Most tests work out of the box, and I ported some basic tests, leaving the following: llvm/test/Instrumentation/AddressSanitizer/lifetime-throw.ll llvm/test/Instrumentation/AddressSanitizer/lifetime-uar-uas.ll llvm/test/Instrumentation/AddressSanitizer/lifetime.ll l...

Hello again, The tool we announced 1.5 months ago has matured quite a bit. In addition to heap out-of-bound and use-after-free bugs it also finds stack overruns/underruns. AddressSanitizer is being actively used by the Chromium developers and already found over 20 bugs: http://blog.chromium.org/2011/06/testing-chromium-addresssanitizer-fast.html Question to the LLVM developers: would you consider adding the AddressSanitizer code to the LLVM trunk? Thanks, --kcc On Tue, May 3,...