One more question:
How could I run asan test just for one shared lib in android using LLVM 
Asan? like libhwui.so, libandroidfw.so..?
The steps I've tried: 
Frist,add LOCAL_ADDRESS_SANITIZER:=true to Android.mk of libhwui.so, the 
directory is frameworks/base/libs/hwui, push the recompiled libhwui.so into 
the android device.
Second, use asan_device_setup script to prepare the device, and I got the 
asan runtime lib libasan_preload.so, asanwrapper, app_process, 
app_process.real in the device, ready.
Third, reboot the device, unfortunately, stuck at the android log. After I 
replace the libhwui.so in the device with the uninstrumented lib, it went 
ok and boot sucessfully.
Why this happened? Am I using it wrong way?

在 2014年7月25日星期五UTC+8下午9时02分24秒,kcc写道:
>
> What's wrong with the existing documentation at 
> https://code.google.com/p/address-sanitizer/ ? 
> Please post specific questions. 
>
> --kcc 
>
> On Fri, Jul 25, 2014 at 4:32 PM, ji wang <[email protected] 
> <javascript:>> wrote: 
> > Especially the way that how to test a shared lib using GCC4.9 asan. 
> thanks 
> > 
> > -- 
> > 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.

Reply via email to