Hi John, Thanks for the pointers,
I gathered all info at this place https://pastebin.com/1sekb62v Not very familiar on the valgrind with cross compiled binaries. Still analysis going on . Thanks vlrk On Wed, Sep 27, 2023 at 10:14 PM John Reiser <jrei...@bitwagon.com> wrote: > On 9/26/23 23:15, ramakanth varala wrote: > > valgrind: A must-be-redirected function > > valgrind: whose name matches the pattern: index > > valgrind: in an object with soname matching: ld-linux.so.3 > > *valgrind: was not found whilst processing* > > *valgrind: symbols from the object with soname: ld-linux.so.3* > > 'index' is identical to 'strchr'. (Run "man 3 index" to see > documentation.) > It might be that the source code for your ld-linux.so has been scoured, > replacing all calls of 'index(' with calls to 'strchr(' instead. > If so, then 'index' will not appear in the symbol table, > and valgrind will have a bug, because: 'index' should be optional. > > Please run your app under 'strace': > strace -f -o strace.out -e trace=file ./my_app args... > and look in file strace.out for two kinds of info: > any line containing "ENOENT" (file not found) > and any line containing "ld-linux" (part of the actual path used > for the run-time dynamic linker.) > Make sure that what you see makes sense. > Also run "readelf --segments ./my_app" and look for the PT_INTERP. > > After discovering the actual path that was used for ld-linux, > then run "readelf --symbols /path/to/ld-linux > symbols-1.txt" > and "readelf --use-dynamic --symbols /path/to/ld-linux > symbols-2.txt" . > Then look in both symbols-[12].txt files to see about 'index' AND 'strchr'. > > > > > > > _______________________________________________ > Valgrind-users mailing list > Valgrind-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/valgrind-users >
_______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
