John, Paul, and Mark
Thank you for the information.
Debian is a bit slow in updating tools. It is very conservative.
Eventually, I obtained the valgrind git code.
(Debian is a bit slow in updating tools. It is very conservative.)
It contained the following.
#if defined(VGO_linux)
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
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)
(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
Dear Paul,
On 2022/05/20 16:58, Floyd, Paul wrote:
Hi Chiaki
Debugging redirection issues isn't normally too slow. Redirection is
done when Valgrind loads the guest executable and libraries.
Run Valgrind with --trace-redir=yes and you should see Valgrind
printing what it finds in
*
Hi Chiaki
Debugging redirection issues isn't normally too slow. Redirection is
done when Valgrind loads the guest executable and libraries.
Run Valgrind with --trace-redir=yes and you should see Valgrind printing
what it finds in
* ld.so, the link loader
* the client executable
* the
Dear Paul,
Thank you for your e-mail and the lucid explanation.
I am sorry that I could not write to you earlier.
There was something wrong with my PC hardware and it took me quite a
while to re-install many software products I regularly use.
I will try to create a short sample. (The whole
Hi
Can you give us
the source of the small reproducer
the versions of Valgrind, Debian, GCC and glibc?
As you mention, functions like strncmp are often optimized to work on
multiple bytes at a time and to take advantage of the fact that memory
will always be allocated in a multiple of say 8
Hi,
I have been analyzing thunderbird mail client under valgrind for sometime.
memcheck has been so useful for me to find memory-related errors.
Thank you for releasing this great tool.
Recently, I noticed an invalid read of 8 bytes warning, which should be
familiar to all of us.
12 matches
Mail list logo
