Re: Question: bug in user code, valgrind or glibc?

John Reiser <[email protected]>
Newsgroups gmane.comp.debugging.valgrind
Message-ID <[email protected]> 
> This indicates that 'strncmp' should be re-directed from ld-linux-x86-64.so.2:

That was done already in valgrind-3.19.0.  The user problem was reported against:
-----
==4295== Memcheck, a memory error detector
==4295== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==4295== Using Valgrind-3.18.1-42b08ed5bd-20211015 and LibVEX; rerun with -h for copyright info
-----
which probably does not contain the fix:
$ git blame shared/vg_replace_strmem.c
947388eb04 (Mike Crowe          2019-09-09 14:16:16 +0100  713)  STRNCMP(VG_Z_LD_LINUX_SO_2, strncmp)
947388eb04 (Mike Crowe          2019-09-09 14:16:16 +0100  714)  STRNCMP(VG_Z_LD_LINUX_X86_64_SO_2, strncmp)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.