On 10/24/18, Padala Dileep wrote:
I see below information
which /opt/mv_7/x86_64/tools/x86_64-gnu/bin/x86_64-montavista-linux-gnu-g++
x86_64-montavista-linux-gnu-g++ (MontaVista Linux G++ 4.7-140716013314) 4.7.0
/opt/mv_7/x86_64/tools/x86_64-gnu/bin/x86_64-montavista-linux-gnu-g++
--print-file-name=libc.so
/opt/mv_7/install/x86_64/montavista/tools/x86_64-gnu/libexec/../x86_64-montavista-linux-gnu/sys-root/usr/lib/../lib64/libc.so
On Wed, Oct 24, 2018 at 8:00 PM Padala Dileep <padala.dil...@gmail.com
<mailto:padala.dil...@gmail.com>> wrote:
Hi John,
Thanks for your response.
Which libc (glibc, uClibc, dietLibc, musl, ...) does this system have?
How to check this one?
Did you do anything to libc after installation, such as strip symbols? No
(Or did the install process itself strip symbols?) No
The libraries generally gets store in a directory /lib on the target, I
have treid setting the VALGRIND_PATH to this library path
Complain to MontaVista: they are unfriendly to valgrind, which means unfriendly
to software developers who use MontaVista products. They have compiled
ld-linux.so.2
such that 'strlen' has been inlined using SSE* instructions. That cannot
possibly
make any difference in the speed of ld-linux, but it is obnoxious to valgrind.
MontaVista should compile ld-linux with -fno-builtin-strlen .
Meanwhile you should use a software development environment that is friendly to
valgrind.
For esoteric technical details see:
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1247026/comments/12
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
