>I could not make static runtime work on older android versions, but >now I don't see any issues with it. Perhaps something with dlopen-ed >libraries? I prefer use shared Asan lib now :), because I've found some issues like when I use static one to check two libs the sametime: "Shadow memory range interleaves with an existing memory mapping."
And Yuri said the GCC Asan android toolchain which I am using now, when we pass -fsanitize=address to the LD_FLAGS, the GCC can arrange proper lib order during link using libasan.so.1 ahead of libc.so, Is that right? Or some difference on Android? 在 2014年7月29日星期二UTC+8下午4时00分05秒，Evgeniy Stepanov写道： > > I could not make static runtime work on older android versions, but > now I don't see any issues with it. Perhaps something with dlopen-ed > libraries? > And you need shared runtime for zygote anyway, unless you build your > own system image. > > On Mon, Jul 28, 2014 at 6:49 PM, ji wang <[email protected] > <javascript:>> wrote: > > How about use static asan runtime? Do the interceptors work with the > static > > runtime? > > Like libasan.a those static lib could compiled into the executable and > the > > test shared lib. > > > > -- > > 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 [email protected] <javascript:>. > > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
