[valgrind] [Bug 476465] AArch64 ARMv8.3 LDAPR/LDAPRH/LDAPRB instructions not supported

2024-02-24 Thread Romain Geissler
https://bugs.kde.org/show_bug.cgi?id=476465 --- Comment #8 from Romain Geissler --- Hi, On this patch implementing only LDAPR, is it going to be pushed in the repo or we are waiting for a patch implementing all 3 variants ? Cheers, Romain -- You are receiving this mail because: You are

[valgrind] [Bug 476895] [aarch64] unhandled instruction 0xF8BFC273

2023-11-15 Thread Romain Geissler
https://bugs.kde.org/show_bug.cgi?id=476895 Romain Geissler changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[valgrind] [Bug 476465] AArch64 ARMv8.3 LDAPR/LDAPRH/LDAPRB instructions not supported

2023-11-15 Thread Romain Geissler
https://bugs.kde.org/show_bug.cgi?id=476465 Romain Geissler changed: What|Removed |Added CC||romain.geiss...@amadeus.com --- Comment #2

[valgrind] [Bug 476895] [aarch64] unhandled instruction 0xF8BFC273

2023-11-15 Thread Romain Geissler
https://bugs.kde.org/show_bug.cgi?id=476895 --- Comment #4 from Romain Geissler --- Duplicate of https://bugs.kde.org/show_bug.cgi?id=476465 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 476895] [aarch64] unhandled instruction 0xF8BFC273

2023-11-15 Thread Romain Geissler
https://bugs.kde.org/show_bug.cgi?id=476895 --- Comment #3 from Romain Geissler --- So after running with gdb, indeed the issue comes from a dynamic linker function (I am using glibc's ld.so): Dump of assembler code for function _dl_name_match_p: 0x04009ba0 <+0>: stp

[valgrind] [Bug 476895] [aarch64] unhandled instruction 0xF8BFC273

2023-11-15 Thread Romain Geissler
https://bugs.kde.org/show_bug.cgi?id=476895 --- Comment #2 from Romain Geissler --- Ah I am totally dumb, you are right ! Sorry, will do that ASAP ! -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 476895] New: [aarch64] unhandled instruction 0xF8BFC273

2023-11-12 Thread Romain Geissler
https://bugs.kde.org/show_bug.cgi?id=476895 Bug ID: 476895 Summary: [aarch64] unhandled instruction 0xF8BFC273 Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Other Status

[valgrind] [Bug 470121] New: Can't run callgrind_control with valgrind 3.21.0 because of perl errors

2023-05-22 Thread Romain Geissler
https://bugs.kde.org/show_bug.cgi?id=470121 Bug ID: 470121 Summary: Can't run callgrind_control with valgrind 3.21.0 because of perl errors Classification: Developer tools Product: valgrind Version: 3.21.0 Platform: Oth

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

2023-04-23 Thread Romain Geissler
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

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

2023-01-30 Thread Romain Geissler
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&action=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

2023-01-30 Thread Romain Geissler
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

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

2023-01-22 Thread Romain Geissler
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

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

2023-01-22 Thread Romain Geissler
https://bugs.kde.org/show_bug.cgi?id=464671 Bug ID: 464671 Summary: Default glibc suppression shouldn't use @GLIBC_VERSION@ anymore with glibc >= 2.34 Classification: Developer tools Product: valgrind Version: 3.21 GIT

[valgrind] [Bug 432102] Support DWARF5

2021-01-26 Thread Romain Geissler
https://bugs.kde.org/show_bug.cgi?id=432102 Romain Geissler changed: What|Removed |Added CC||romain.geiss...@amadeus.com -- You are

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2018-05-27 Thread Romain Geissler
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #15 from Romain Geissler --- Yes I am using it already, and it's working. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2018-05-16 Thread Romain Geissler
https://bugs.kde.org/show_bug.cgi?id=372347 Romain Geissler changed: What|Removed |Added CC||romain.geiss...@amadeus.com --- Comment #13