similar to: [LLVMdev] ASan for Android Applications

You 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

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

I have simple standalone ASan examples working on Android, and now I'd like to try using ASan with 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

Hi, We are rebasing our audio compression subsystem using OPUS rather than SPEEX. The platform is Android but this piece is written in C code: we need to support armv5/armv7/x86 architectures.... and we use the released opus-1.1beta package from here<http://downloads.xiph.org/releases/opus/opus-1.1-beta.tar.gz>. A lot of our OPUS build system + code to drive the audio compression has been

> 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 += -fsanitize=address TARGET_LDFLAGS +=-fsanitize=address -target

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*

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

Along the same lines as the last question - how can I get to functions like MakeOpenFile via Win32API? It doesn''t seem to be exported by msvcrt-ruby18. Possible? Or am I out of luck? Dan This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have

I yum updated yesterday and it updated chrome from 44.x to 45.x. It runs but it has errors going to web pages and won't load its own settings/extension pages either. I ran chrome from the command-line and see these errors: $ google-chrome libGL error: dlopen /usr/lib/dri/swrast_dri.so failed (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory) libGL error:

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

Hi We want to use our existing engine sourcecode to build Java applications. Our core engine is written in C/C++ and has hooks to platform specific functions which we have filled in for lots of platforms so far, PC, DS, PS2, PSP, XBOX, IPHONE etc. All of which can use C/C++ as their compiler. However now we want to target Android platforms, so we are looking into converting the main body of

Hi, I''ve got a newbie question--sorry if this is covered elsewhere, I parsed through the archives for awhile and didn''t see it. I''d like to listen for whenever a file is renamed (e.g. foo.txt -> foo.old) and then magically change it back. This sounds odd, but I''m working with a stubborn application and this will actually make things work nice. So, if I do:

Hi Jack, I'm almost there with Android..... I've actually got the static and dynamic libraries built. I'm choking on the test suite. Do you want to take a shot at working around Android and [embedded, lame] STLport? I would try removing the call to rend() in std::map<_Key, _Tp, _Compare, _Alloc>::rend(). But I really should not modify program code. Fiddling with a Makefile is

When trying to play vorbis or opus files that have large cover sizes >1MB on android 8.0 built in player, they fail to play. Removing the cover allows them to play.  Has anyone encountered this before or know if it is a known android or opus/vorbis bug?

Hello, I would like to share my successful bring-up of LLVM/clang-built Linux ARM(32-bit) hammerhead kernel for Android running on my Nexus 5 smartphone. After having successfully brought up LLVM/clang-built Linux kernel(since v4.15.7 to the most recent v4.17) on x86_64, I was interested in accomplishing the same on the ARM platform of my Nexus 5 - Android smartphone. So, here is the complete

> 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

Hats off to the Android NDK team! http://developer.android.com/tools/sdk/ndk/index.html Important changes: * Added the Clang 3.1 compiler to the NDK. The GNU Compiler Collection (GCC) 4.6 is still the default, so you must explicitly enable the Clang compiler option as follows: * For ndk-build, export NDK_TOOLCHAIN_VERSION=clang3.1 or add this environment variable setting

> The main advantage of the clang-built Android ARM(32-bit) hammerhead kernel for my Nexus 5 has been the better battery usage when compared to that of gcc-built kernel, with the same kernel config and hardware(my Nexus 5 Android Smartphone). Details of the same can be found below. To be fair, the GCC version which comes with the android ndk has not been updated for four years, while the clang

Hey Guys, I'm working on a project in Android related to System-level Audio DSP Effects for Tuning Android Audio. I want to leverage Faust ( https://faust.grame.fr/) to allow users to program their own filters. Faust provides a libfaust implementation which includes a JIT Compiler which leverages LLVM and seems to be the best path for me to use. Unfortunately I'm having problems