Hi,
Change of information:
After recompiling valgrind, now I _do_ have __libc_freeres symbol in
vgpreload_core-arm-linux.s (http://pastebin.com/LijCA8Km) but I still got
cannot "locate __libc_freeres" error.
integrated into your environment (what is ldd.RTLDLIST ?) or that the
> PT_INTERP
> /system/bin/linker does not observe all the conventions regarding:
> ${rtld} --verify "$file"
> This means that ldd does not work. [What facility does your environment
> provide
> for listing the actual {libname ==> file} resolution and the transitive
> closure
> of DT_NEEDED shared libraries for an app?]
>
You are right, in the ldd.RTLDLIST there are
only RTLDLIST="/lib/ld-linux.so.2 /lib64/ld-linux-x86-64.so.2" so I suppose
it's normal that ldd did not work for android's linker. However I do have
readelf -d that works as I posted in earlier message that will also list
down the shared library.
> Yes, the environment is different enough to cause problems. All of the
> GLOBAL *UND* [undefined] symbols from vgpreload_memcheck-arm-linux.so
> must be resolvable.
>
As posted above http://pastebin.com/LijCA8Km shows that there are some
symbols that are undefined. I see that in x86, these symbols are also
undefined. I don't really know what happens in the background if a symbol is
undefined but there is no problem running valgrind on x86 with these
undefined symbol.
--
Wan Mohd Fairuz WAN ISMAIL
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
