similar to: ASAN

If running ASan on the host architecture, we can symbolize output with: export LLVM_SYMBOLIZER_PATH=`which llvm-symbolizer` ./myInstrumentedProgram but on Android symbolizing is more complex. The bash script below is a "hello world" for symbolizing ASan output on Android. Is there a simpler way to do this? # Execute the test and save its output adb push

For the same reason we use shared runtime on OSX. We intercept libc calls by declaring a function with the same name in the sanitizer runtime library. Glibc loader puts main executable early in the symbol lookup order, which lets us interpose symbols from shared libraries with symbols from statically linked sanitizer runtime. Android (and AFAIK most other platforms) does not allow that, which is

On Wed, Oct 30, 2013 at 2:08 PM, Greg Fitzgerald <garious at gmail.com> wrote: > If running ASan on the host architecture, we can symbolize output with: > > export LLVM_SYMBOLIZER_PATH=`which llvm-symbolizer` > ./myInstrumentedProgram > > but on Android symbolizing is more complex. The bash script below is > a "hello world" for symbolizing ASan output

Thanks for letting me know that this is in the works. This is something that would make running ASan (and all other sanitizers I assume) quite a bit more appealing on Android. If there's anything I can do to help, please let me know. If you'd like to discuss in person, I'll be at the Developers' Meeting next week. -Greg On Thu, Oct 31, 2013 at 1:58 PM, Alexey Samsonov

> Static runtime will only intercept calls from the main executable, but > not from any libraries. This may work for simple standalone programs, > but you may run into puzzling failures. What type of failures do you mean? Does the symbol mismatch break assumptions in the ASan runtime? It's easy to imagine, for example, ASan missing use-after-free bugs because the call to free() is

> Are you suggesting that we should be more aggressive by default (i.e. without -fvisibility=hidden or any new options)? > I believe that will be too aggressive for class LTO visibility. > It is common to override a virtual functions across shared library boundaries I'm myself a fan of GCC's conservative approach so I'd agree with you on that. But regardless of my personal

+eugenis@ On Sat, Sep 21, 2013 at 4:58 AM, Greg Fitzgerald <garious at gmail.com> wrote: > Why does compiler-rt ship a shared object for ASan on Android instead > of a static library? Would statically linking ASan on Android at > least be safe for standalone executables? > > And if I'm wanting to use ASan in C++ code that is invoked from an > APK, can I statically

Why does compiler-rt ship a shared object for ASan on Android instead of a static library? Would statically linking ASan on Android at least be safe for standalone executables? And if I'm wanting to use ASan in C++ code that is invoked from an APK, can I statically link ASan? If not, what is the reason we need to preload Dalvik with the ASan shared object? I assume static linking here

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, I am trying to preload two shared libraries while running Qemu using libvirt. To preload the shared libraries I have added an environment variable in the $domain.xml file with the following command: ``` virt-xml generic --edit --confirm --qemu-commandline

Hello, Recently we tried to streamline our toolchain by removing some GNU tools with LLVM tools to avoid having multiple copies of strip, nm, ar and similar tools. Today we ran into a really strange issue where shared objects where not loadable. We where able to track this down to llvm-strip with default arguments creating a shared object that doesn't load correctly. It works if we switch

I've used that patch to close the hole. This patch is temporary and doesn't fix real trouble maker - problem in new version in getenv() (after 6.3 it got changed to something monstrous and non-working right if environment has only one variable), hope it will get fixed soon. *** rtld.c.orig Tue Dec 1 16:55:13 2009 --- rtld.c Tue Dec 1 16:55:55 2009 *************** *** 357,374 ****

On 2020-05-09 19:41, Liam O'Toole wrote: > On Sat, 09 May, 2020 at 16:02:17 -0400, mark wrote: >> Hi, folks, >> >> Updated CentOS 7 the other day. Updated zoom last night. Ancient (15 yr >> old) USB camera, Logitech QuickCam Express. >> >> If I run LD_PRELOAD=/usr/lib64/libv4l/v4l2convert.so cheese, I get video. >> Zoom, with or without the

Hi, folks, Updated CentOS 7 the other day. Updated zoom last night. Ancient (15 yr old) USB camera, Logitech QuickCam Express. If I run LD_PRELOAD=/usr/lib64/libv4l/v4l2convert.so cheese, I get video. Zoom, with or without the LD_PRELOAD - no video. I've tried stracing zoom, and created a file /etc/ld.so.preload, with the contents of /usr/lib64/libv4l/v4l2convert.so, and in

> 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

On Wed, Oct 19, 2016 at 6:24 PM, Benjamin Kramer via llvm-dev < llvm-dev at lists.llvm.org> wrote: > In terms of performance shared_ptr has a number of disadvantages. One > is that it always uses atomics even though most IntrusiveRefCntPtrs > are used in single-threaded contexts. Another is weak_ptr adding a lot > of complexity to the implementation, IntrusiveRefCntPtr

On Wed, Oct 19, 2016 at 9:31 PM, Mehdi Amini via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > On Oct 19, 2016, at 11:14 AM, Bruce Hoult via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > On Wed, Oct 19, 2016 at 6:24 PM, Benjamin Kramer via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> In terms of performance shared_ptr has a number of

Sorry for the slow replies. I'm out on vacation this week. Alexey wrote: > If you want to test the sanitizer runtiume library "during development", > you should verify that it works with the Clang at hand. I want to test an implementation of libraries, not that clang links a library in its install directory. We only need one clang test for the latter (not 100) and that

I'm running libvirt 1.0.1 and qemu 1.3. I see the following error of libvirtd startup: 2013-01-19 04:51:06.183+0000: 1459: error : virCommandWait:2287 : internal error Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin HOME=/ /usr/bin/kvm -help) unexpected exit status 1 This is indeed what the return code seems to be for that command. This this just a

Hi, I am trying to compile a dynamic loader using LLVM. Part of the IR for this loader looks like this: @_rtld_local = hidden alias %struct.rtld_global* @_rtld_global @_rtld_global = unnamed_addr global %struct.rtld_global { ... } The purpose of _rtld_local is to allow _rtld_global to be referenced without using the GOT, as this global is accessed before the dynamic loader initialises the GOT.