On 9/28/23 20:55, ramakanth varala wrote:
I gathered all info at this place https://pastebin.com/1sekb62v <https://pastebin.com/1sekb62v>
Looking at the previous messages of the thread in [Valgrind-users] mailing list, I don't see any information about the context in which you are working. Specifically: Which version of valgrind ? (Run "valgrind --version".) Which hardware? Which operating system and version? Which Linux distribution and software [cross-]development environment? Which compiler and version, and which C run-time library and version? Some of that info is *required* in order to help you, and all of it makes it much easier for maintainers to understand what the problem might be. From the pastebin posting it apears that you are running Linux on a 32-bit ARM system which uses /lib/ld-linux.so.3 as the run-time dynamic linker. But which version of the development environment, compiler, and run-time C library? Yes, it might really matter. Bottom line: give enough information so that a maintainer can reproduce the problem that you see. Getting down to specifics:
$ readelf --use-dynamic --symbols ./lib/ld-linux.so.3 > /home/labuser/rk/symbols-2.txt
The use of "./lib/ld-linux.so.3" instead of "/lib/ld-linux.so.3" [the difference is a leading dot '.' or not] triggers alarm bells. You must be *ABSOLUTELY CERTAIN* that those two files have identical contents. Particularly with "cross-system" environments, it is trivially easy for them to differ inadvertently or on purpose. Run both 'cmp' and 'sha256sum' to be sure that the contents are the same. If the contents are not the same, then you must start over from the beginning. Using a text editor on the contents of the pastebin posting: ===== :g/index$/p 857: 0001a300 204 FUNC LOCAL DEFAULT 10 index :g/index$/?Symbol table?p Symbol table '.symtab' contains 988 entries: :g/index$/?$ cat?p $ cat /home/labuser/rk/symbols-1.txt ===== Therefore the symbol 'index' does exist in the link-time symbols-1.txt, but not in the run-time symbol table symbols-2.txt. So if the real /lib/ld-linux.so.3 has been stripped in order to save space, then 'index' will disappear, and valgrind will not be able to find it. ===== :g/strchr$/p 933: 0001a300 204 FUNC LOCAL DEFAULT 10 strchr :g/strchr$/?Symbol table?p Symbol table '.symtab' contains 988 entries: :g/strchr$/?$ cat?p $ cat /home/labuser/rk/symbols-1.txt ===== Therefore 'strchr' is a synonym for 'index', having the same value 0x0001a300 and the same properties, but a different name, and a different position in the link-time symbol table. Overall conclusion: you have found a bug in valgrind, namely 'index' is optional, and not required as demanded by valgrind. (Which version of valgrind? :-) ) Please file a bug report, following the directions at https://valgrind.org/support/bug_reports.html You will need to supply all the version info of the various pieces, and the analysis of which symbols really are present, and _where_. _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
