Hi,
On Sat, May 21, 2022 at 02:42:22AM -0700, John Reiser wrote:
> > 143:39.43 GECKO(115765) ==115769== Invalid read of size 8
> > 143:39.64 GECKO(115765) ==115769==at 0x4021BF4: strncmp (strcmp.S:175)
> > 143:39.64 GECKO(115765) ==115769==by 0x400655D: is_dst
> > (dl-load.c:214)
>
>
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
AuthorDate: Mon Sep 9 14:16:16 2019
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==
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.
The preferred way is to create a bug report, attach the large file to the bug
report,
then post
