Hi Paul, Thanks a lot for reply and inputs.
As said for some it works fine . In my target board we have busybox binary , this works very fine with valgrind. I mean if "ld-linux.so.3 needs to have symbols" ,does this mean busy box does not use this linker / loader?. Where as for others it gives error as shown before?. when I do readelf -S /lib/ld-linux.so.3 , it shows [21] .debug_aranges PROGBITS 00000000 0218f0 0000a0 00 0 0 8 [22] .debug_info PROGBITS 00000000 021990 000a81 00 0 0 1 [23] .debug_abbrev PROGBITS 00000000 022411 0001b2 00 0 0 1 [24] .debug_line PROGBITS 00000000 0225c3 00037f 00 0 0 1 [25] .debug_frame PROGBITS 00000000 022944 000608 00 0 0 4 [26] .debug_str PROGBITS 00000000 022f4c 0011cf 01 MS 0 0 1 [27] .debug_loc PROGBITS 00000000 02411b 0002fb 00 0 0 1 Will this confirm like it has debugging symbols. You are inputs are very helpful. Thanks vlrk On Wed, Sep 27, 2023 at 1:17 PM Paul Floyd <pjfl...@wanadoo.fr> wrote: > > On 27/09/2023 08:15, ramakanth varala wrote: > > > > Not sure enough , what exactly missing , Any inputs in this will be highly > appreciated. > > *valgrind: symbols from the object with soname: ld-linux.so.3* > > Valgrind is looking for symbols in ldrt, the runtime link loader. > > Either ld-linux.so.3 needs to have symbols or there needs to be a separate > debuginfo file. > > If the debuginfo is in a non-standard location try > --extra-debuginfo-path=path and perhaps also > --allow-mismatched-debuginfo=yes > > A+ > > Paul > >
_______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
