search for: fuzzpy

...======== Flag: verbosity 3 Flag: use_traces 1 Flag: timeout 100 Flag: max_len 16384 Seed: 3259211893 PreferSmall: 0 #0 READ units: 4975 exec/s: 0 #1 pulse cov: 32410 bits: 30791 indir: 714 units: 4975 exec/s: 0 NEW0: 32410 L 13869 ==31301==AddressSanitizer CHECK failed: /home/brian/src/fuzzpy/llvm_src/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_coverage_libcdep.cc:467 "((n % 16)) == ((0))" (0x1, 0x0) #0 0x11d3b7 in __asan::AsanCheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) /home/brian/src/fuzzpy/llvm_src/llvm/projects/compil...

Kostya, Here's the git repo: https://bitbucket.org/ebadf/fuzzpy I've only tested it on arm7 and x86_64 linux, I expect there's a good chance it may not work on other OSs. If you can build it successfully ("./build.sh", requires clang and clang++ in your path), then you should run the "testemail" case like so: while true; do ITERS=...

...he workaround though. On Dec 3, 2015 1:12 PM, "Kostya Serebryany" <kcc at google.com> wrote: > > > On Wed, Dec 2, 2015 at 7:17 PM, Brian Cain <brian.cain at gmail.com> wrote: > >> Kostya, >> >> Here's the git repo: https://bitbucket.org/ebadf/fuzzpy >> >> I've only tested it on arm7 and x86_64 linux, I expect there's a good >> chance it may not work on other OSs. >> >> If you can build it successfully ("./build.sh", requires clang and >> clang++ in your path), then you should run the "...

...ct that it happened in phase 3 suggests some hardware malfunction of mine? Or are there tests executed on phase 3 that aren't attempted on earlier phases? $ CC=clang CXX=clang++ ./test-release.sh -release 3.7.1 -rc 2 -j1 -openmp -triple armv7l-ubuntu15.10-linux-gnueabihf ... cd /home/brian/src/fuzzpy/llvm_src/llvm/utils/release/rc2/Phase3/openmp/src && /home/brian/src/fuzzpy/llvm_src/llvm/utils/release/rc2/Phase3/Release/llvmCore-3.7.1-rc2.install/usr/local/bin/clang -o test-touch-rt/test-touch /home/brian/src/fuzzpy/llvm_src/llvm/utils/release/rc2/openmp.src/runtime/src/test-touch.c -l...

Hi, There was one problem in -rc1, so we had to do another release candidate. -rc2 has now been tagged and is ready for testing. -Tom