Re: [Valgrind-users] Question: bug in user code, valgrind or glibc?

[John R. <jr...@bi...>]

> This looks like https://bugs.kde.org/show_bug.cgi?id=434764
> iconv_open causes ld.so v2.28+ to use optimised strncmp
> 
> Which was recently (but after 3.19.0) fixed by merging this commit:
> 
> commit 947388eb043ea1c44b37df94046e1eee790ad776
> Author:     Mike Crowe <ma...@mc...>
> AuthorDate: Mon Sep 9 14:16:16 2019 +0100
> Commit:     Mark Wielaard <ma...@kl...>
> CommitDate: Sat May 14 00:41:18 2022 +0200
> 
>      Intercept strncmp for glibc ld.so v2.28+
>      

The C standard claims that all function names that begin with
'str' or 'mem' are reserved, and that language processors (compilers,
valgrind, ...)  may assume that such names designate the Standard functions.
If so, then valgrind's interception code is too picky about the context
for re-directing these functions; just use
      STRNCMP("*", strncmp)
etc. to re-direct them all.