On Thu, May 18, 2017 at 3:49 PM, 'Evgenii Stepanov' via address-sanitizer <address-sanitizer@googlegroups.com> wrote: > Oh, and the downside is slow startup. With the wrap property, any > process startup takes several extra seconds to reload all the base > classes. > > On Thu, May 18, 2017 at 12:48 PM, Evgenii Stepanov <euge...@google.com> wrote: >> Hi, >> >> There is a system property that lets you prepend anything to the >> zygote command line for a specific application, "wrap.<app-name>". It >> requires a rooted device, but does not require remounting system r/w.
Thanks, that should be helpful. >> >> In theory, this requirement could be relaxed by allowing wrapping apps >> even on a locked device based on the app manifest - some property like >> "debuggable". That requires changing android platform source. That seems like it would be even better, although I question whether android would be receptive to that sort of change, given potential security implications, etc. >> >> https://source.android.com/devices/tech/debug/asan#using_the_wrap_property >> >> On Thu, May 18, 2017 at 8:29 AM, Francis Ricci <francisjri...@gmail.com> >> wrote: >>> Hi all! >>> >>> Historically, I've always used ASan on a rooted/flashed device, as the >>> asan_device_setup script requires root access. Is it possible (even in >>> theory, or with some extra work in the codebase) to run ASan on a non-rooted >>> device? I know you can for a simple C++ binary, since you can just run that >>> via the command-line with LD_PRELOAD. But I know things are quite a bit more >>> complex for apps, since you can't over-write app_process without a r/w >>> system partition. What I've found online so far mostly points to shadow >>> memory and libc issues. >>> >>> It would be quite valuable for me to be able to run ASan on apps on >>> non-rooted phones (even if I could only get a subset of checks to work), so >>> I'd be willing to put in a fair amount of work to make it happen, if it's >>> the sort of thing that could be possible. >>> >>> Thanks! >>> Francis >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "address-sanitizer" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to address-sanitizer+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "address-sanitizer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to address-sanitizer+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to address-sanitizer+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
