[valgrind] [Bug 464671] Default glibc suppression shouldn't use @GLIBC_VERSION@ anymore with glibc >= 2.34

https://bugs.kde.org/show_bug.cgi?id=464671 --- Comment #8 from Romain Geissler --- (In reply to Mark Wielaard from comment #7) > Is this just for strcmp in ld.so? > In that case the intercept in shared/vg_replace_strmem.c should in theory > fix that. Hi, Yes in my case it happens only for

[valgrind] [Bug 464671] Default glibc suppression shouldn't use @GLIBC_VERSION@ anymore with glibc >= 2.34

https://bugs.kde.org/show_bug.cgi?id=464671 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #7 from Mark

[valgrind] [Bug 464671] Default glibc suppression shouldn't use @GLIBC_VERSION@ anymore with glibc >= 2.34

https://bugs.kde.org/show_bug.cgi?id=464671 --- Comment #6 from Sam James --- I'd offer but I don't have access to older glibcs easily either. I'd love for this to get into the next release though. I can probably try with Docker if required. -- You are receiving this mail because: You are

[valgrind] [Bug 464671] Default glibc suppression shouldn't use @GLIBC_VERSION@ anymore with glibc >= 2.34

https://bugs.kde.org/show_bug.cgi?id=464671 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail

[valgrind] [Bug 464671] Default glibc suppression shouldn't use @GLIBC_VERSION@ anymore with glibc >= 2.34

https://bugs.kde.org/show_bug.cgi?id=464671 --- Comment #5 from Paul Floyd --- I'd rather leave this to Mark as I only have 1 Fedora machine to test on (with glibc 2.36) -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 464671] Default glibc suppression shouldn't use @GLIBC_VERSION@ anymore with glibc >= 2.34

https://bugs.kde.org/show_bug.cgi?id=464671 --- Comment #4 from Romain Geissler --- Created attachment 155802 --> https://bugs.kde.org/attachment.cgi?id=155802=edit Pach (doesn't work for glibc < 2.34) -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 464671] Default glibc suppression shouldn't use @GLIBC_VERSION@ anymore with glibc >= 2.34

https://bugs.kde.org/show_bug.cgi?id=464671 --- Comment #3 from Romain Geissler --- Hi, On my side I will test this, which isn't good in general, but shall be ok for people like me using glibc >= 2.34. I have replaced libdl by libc as in glibc 2.34 libdl is now an empty library, all its symbols

[valgrind] [Bug 464671] Default glibc suppression shouldn't use @GLIBC_VERSION@ anymore with glibc >= 2.34

https://bugs.kde.org/show_bug.cgi?id=464671 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #2 from Paul Floyd

[valgrind] [Bug 464671] Default glibc suppression shouldn't use @GLIBC_VERSION@ anymore with glibc >= 2.34

https://bugs.kde.org/show_bug.cgi?id=464671 --- Comment #1 from Romain Geissler --- Seems related to https://bugs.kde.org/show_bug.cgi?id=439590 which resulted in this commit: https://sourceware.org/git/?p=valgrind.git;a=commitdiff;h=a1364805fc74b5690f763033c0c9b43f27613572#patch3 In particular