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

[ISHIKAWA,chiaki <ish...@yk...>]

Hi,

I sent a log of redirect information to both Paul and John since the log 
was too large was mailing list.

I wonder what would be the preferred public sharing site for such a 
purpose these days.

TIA

Chiaki

On 2022/05/21 0:57, John Reiser wrote:
>> (Wait, I see  "279:13.65 GECKO(392456) ==392459==    by 0x488D2D3: 
>> dlopen@@GLIBC_2.2.5 (dlopen.c:87)"
>> Version 2.2.5 is not the same as the version reported for glibc. Hmm? )
>
> The "@@GLIBC_2.2.5" is the linking symbol version assigned by glibc.
> This effectively is an ABI version, and the ABI for dlopen
> has not changed for many years, even though other parts of
> glibc have changed; one recent release is glibc-2.33.
>
> The real key to Chiaki's problem is:
>> 279:13.65 GECKO(392456) ==392459== Invalid read of size 8
>> 279:13.65 GECKO(392456) ==392459==    at 0x4021BF4: strncmp 
>> (strcmp.S:175) 
> which says that this 'strncmp' was not re-directed by valgrind.
> Re-running valgrind with the additional command-line parameter
> "--trace-redir=yes" will help provide more information.
> Probably the run can be stopped after the first actual dlopen,
> because that should be enough to trigger all the redirections
> that matter here.
>
>
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users