The first thing to try is to compile and use a more recent valgrind version. (3.18 is something like 4 years old while 3.24 is from Oct 24).
Thanks Philippe On Wed, 2025-01-29 at 19:03 +0530, kiran hardas wrote: > Hi Team, > > Good Evening, > > I need some support in debugging an issue in Valgrind 3.18. > > I have an application which I am trying to check with Valgrind tool for > memory issues. I > have the valgrind source code which is compiled and built along with my > application > using same set of libraries. But while checking with valgrind tool i get an > invalid > address error in libc library (mostly implying null pointer > dereferencing/free) and > valgrind is terminating. I am unable to find the exact place in glibc code > where this > error is coming from and need any help which you can provide. > > Please find further details below, > > $ ./usr/test/bin/valgrind --version -v > valgrind-3.18.1-42b08ed5bd-20211015 > > GNU/Linux 5.4 > Glibc 2.40 > gcc 14.2 > binutils 2.43 > > This same valgrind was working when i was using glibc 2.23 but giving this > error when i > upgraded glibc to 2.40 > For valgrind 3.18 i have applied rseq patches and nop code error (0x2E 0x8D > 0xB4 0x26) > patches also required for latest glibc 2.40. > > Error log snippet: > ------------------------ > ... > ... > ==13089== > --13089-- REDIR: 0x1f749f60 (libc.so.6:???) redirected to 0x1e59bd70 (strcmp) > ==13089== Jump to the invalid address stated on the next line > ==13089== at 0x0: ??? > ==13089== by 0x1F607366: ??? (in /lib/libc-2.40.so) > ==13089== by 0x1F607423: (below main) (in /lib/libc-2.40.so) > ==13089== Address 0x0 is not stack'd, malloc'd or (recently) free'd > ==13089== > ==13089== > ==13089== Process terminating with default action of signal 11 (SIGSEGV): > dumping core > ==13089== Bad permissions for mapped region at address 0x0 > ==13089== at 0x0: ??? > ==13089== by 0x1F607366: ??? (in /lib/libc-2.40.so) > ==13089== by 0x1F607423: (below main) (in /lib/libc-2.40.so) > ==13089== > > > Approaches tried > ----------------------- > 1. I reduced the optimisation level in glibc to -O1, but still no further > symbol details > are available > 2. The core file generated for valgrind crash is also not showing any symbol > details at > crash point. (only showing ??) > 3. Tried adding more option to valgrind like --track-origins=yes , > --read-var-info=yes . > But not giving any more info for the error. > > > I would appreciate any pointers team can provide in debugging this issue. > > Thanks in advance > > Regards, > Kiran H. > > _______________________________________________ > 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
