search for: jellybean

...se 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). What run-time environments are known to work? Thanks, Greg

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

Some updates: First, thanks so much for creating these test suites. Troubleshooting is going very quickly! > There is some flakiness in SanitizerCommon.SpinMutex test. Yes, I'm seeing that too. SpinMutexTry as well. Should these be disabled? > ARM JellyBean works over here. I found a configuration that works well on JB 4.1.2 and 4.2.2. The trick is to build the ASan *runtime* with *CMake*. If you build the runtime using the Make build, the test suite falls over. Also, lots of tests fail when running on the Android Emulator. This is a convenient e...

From: http://address-sanitizer.googlecode.com/svn-history/r1624/wiki/Android.wiki > AddressSanitizer is fully supported in AOSP starting with JellyBean release. To run > applications built with ASan you'll need an -eng build of Android. > > To build any part of Android system with ASan, add > LOCAL_ADDRESS_SANITIZER:=true to the appropriate Android.mk. I don't see that string 'LOCAL_ADDRESS_SANITIZER' in the latest NDK...

...h the Android build system. I'm building the release_33 branch of llvm+clang+compiler-rt with CMake. To test, I'm looking at libjpg, because with just a small change its Android.mk it compiles in a few seconds and without needing any additional dependencies. When I run 'djpeg' on JellyBean, ASan reports the error message below. Can you please help me interpret it? Do you know what I might be doing wrong? $ adb shell "cd /data/data && ASAN_OPTIONS=debug=1,verbosity=1 LD_PRELOAD=libclang_rt.asan-arm-android.so LD_LIBRARY_PATH=. ./djpeg ./testimg.jpg" ==28210==Pars...

...u are citing the "Android platform workflow" section, which is about sanitizing components of the Android system itself. For NDK apps, see "Android NDK workflow" in the same document. You need -eng build because preloading libraries into dalvik vm is not allowed in user builds. JellyBean includes several bugfixes in the dynamic loader that asan needs. Was there any useful output in adb logcat when your program crashed? On Fri, Jun 21, 2013 at 4:47 AM, Greg Fitzgerald <garious at gmail.com> wrote: > From: > http://address-sanitizer.googlecode.com/svn-history/r1624/wiki...

> When I run 'djpeg' on JellyBean, ASan reports the error message below. > > ==28210==Shadow memory range interleaves with an existing memory > mapping. ASan cannot proceed correctly. ABORTING. Got figured out. I needed to use TARGET_LDFLAGS. LOCAL_LDFLAGS seems to be ignored in my clang build. LOCAL_CFLAGS += -fsaniti...

...as well. Should these be disabled? > There is an issue in the spinlock on ARM: it's implemented with plain non-atomic loads and stores. It seems that android ndk does not have the atomics we need for this, and we did not have time to do an asm implementation yet. > > > > ARM JellyBean works over here. > > I found a configuration that works well on JB 4.1.2 and 4.2.2. The > trick is to build the ASan *runtime* with *CMake*. If you build the > runtime using the Make build, the test suite falls over. > > Also, lots of tests fail when running on the Android Emula...

Evgeniy, thanks for your help. > You need -eng build because preloading libraries into dalvik vm is not > allowed in user builds. JellyBean includes several bugfixes in the > dynamic loader that asan needs. Do you have the sha1 hashes for any of those patches? I might be able to track down a build that includes them. > Was there any useful output in adb logcat when your program crashed? Yes, I've been getting some nice h...

...analysis" and names Revolution Analytics a "Cool Vendor": http://bit.ly/kTN8lV Other non-R-related stories in the past month included: the origin of the aphorism, "The plural of anecdote is not data" -- or is it? (http://bit.ly/lg7XuB); P-values, multiple comparisons, and jellybeans (http://bit.ly/imx1Q3); visualizing tax brackets (http://bit.ly/lLmQSc) and an infographic on how taxes are spent (http://bit.ly/knMqmw); browsing the San Andreas Fault (http://bit.ly/lMHumV); 250 years of Bayes' Theorem (http://bit.ly/leAHxd) and gardening with Gamma rays (http://bit.ly/lbvGN...

> What version of glibc are you building with on x86? 2.11.1 for 64-bit x86 linux $ ldd --version ldd (Ubuntu EGLIBC 2.11.1-0ubuntu7.8) 2.11.1 On Fri, May 31, 2013 at 8:24 AM, Sergey Matveev <earthdok at google.com> wrote: > Those changes shouldn't affect ARM at all, since everything is under #if > defined(__i386__) || defined(__x86_64__). > > What version of glibc are

Those changes shouldn't affect ARM at all, since everything is under #if defined(__i386__) || defined(__x86_64__). What version of glibc are you building with on x86? On Fri, May 31, 2013 at 7:16 PM, Greg Fitzgerald <garious at gmail.com> wrote: > The failures happen on x86 Linux, Ubuntu Lucid. On ARM Android, my > example code segfaults, whereas before it worked. I