[clazy] [Bug 490549] clazy 1.12 does not compile with (the upcoming) clang 19

https://bugs.kde.org/show_bug.cgi?id=490549 --- Comment #2 from Peter Klotz --- Created attachment 175215 --> https://bugs.kde.org/attachment.cgi?id=175215&action=edit A patch against clazy 1.13-20240928 This patch makes clazy 1.13-20240928 (git r

[clazy] [Bug 490549] clazy 1.12 does not compile with (the upcoming) clang 19

https://bugs.kde.org/show_bug.cgi?id=490549 --- Comment #1 from Peter Klotz --- Created attachment 175214 --> https://bugs.kde.org/attachment.cgi?id=175214&action=edit A patch against clazy 1.12 This patch makes clazy 1.12 work together with clang 19. -- You are receiving this mail

[clazy] [Bug 490549] New: clazy 1.12 does not compile with (the upcoming) clang 19

https://bugs.kde.org/show_bug.cgi?id=490549 Bug ID: 490549 Summary: clazy 1.12 does not compile with (the upcoming) clang 19 Classification: Developer tools Product: clazy Version: unspecified Platform: RedHat Enterpris

[valgrind] [Bug 476553] RPM build of Valgrind 3.22.0 fails under RHEL8

https://bugs.kde.org/show_bug.cgi?id=476553 --- Comment #4 from Peter Klotz --- Created attachment 163037 --> https://bugs.kde.org/attachment.cgi?id=163037&action=edit Patch needed to package libexec content As mentioned earlier in the bug, this patch is needed to properly package

[valgrind] [Bug 476553] RPM build of Valgrind 3.22.0 fails under RHEL8

https://bugs.kde.org/show_bug.cgi?id=476553 --- Comment #3 from Peter Klotz --- Created attachment 163036 --> https://bugs.kde.org/attachment.cgi?id=163036&action=edit Workaround to packge gdb Python script files It seems gdb in RHEL8 is not too old for packaging valgrind-monitor-def

[valgrind] [Bug 476553] RPM build of Valgrind 3.22.0 fails under RHEL8

https://bugs.kde.org/show_bug.cgi?id=476553 --- Comment #2 from Peter Klotz --- Hi Mark Thanks, your suggestion brought me a lot closer to building the RPM. However at the end I got messages about unpackaged files: > Checking for unpackaged file(s): /usr/lib/rpm/check-files > /hom

[valgrind] [Bug 476553] New: RPM build of Valgrind 3.22.0 fails under RHEL8

https://bugs.kde.org/show_bug.cgi?id=476553 Bug ID: 476553 Summary: RPM build of Valgrind 3.22.0 fails under RHEL8 Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Linux St

[valgrind] [Bug 432801] Valgrind 3.16.1 reports a jump based on uninitialized memory somehow related to clang and signals

https://bugs.kde.org/show_bug.cgi?id=432801 --- Comment #46 from Peter Klotz --- Is there a chance that the available fix for this issue will make it into the upcoming Valgrind version (3.18 I assume)? -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 432801] Valgrind 3.16.1 reports a jump based on uninitialized memory somehow related to clang and signals

https://bugs.kde.org/show_bug.cgi?id=432801 --- Comment #15 from Peter Klotz --- Hi Eyal Your patch indeed solves the Valgrind error that occurred in the original program. Really great work, thanks a lot! -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 432801] Valgrind 3.16.1 reports a jump based on uninitialized memory somehow related to clang and signals

https://bugs.kde.org/show_bug.cgi?id=432801 --- Comment #10 from Peter Klotz --- Hi Eyal Thank you very much for the analysis of the problem! Will you open an LLVM issue? -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 432801] Valgrind 3.16.1 reports a jump based on uninitialized memory somehow related to clang and signals

https://bugs.kde.org/show_bug.cgi?id=432801 --- Comment #4 from Peter Klotz --- Created attachment 135597 --> https://bugs.kde.org/attachment.cgi?id=135597&action=edit Disassembly of main() when Valgrind shows no warning The second sigaction() call was removed. In this case the assemb

[valgrind] [Bug 432801] Valgrind 3.16.1 reports a jump based on uninitialized memory somehow related to clang and signals

https://bugs.kde.org/show_bug.cgi?id=432801 --- Comment #3 from Peter Klotz --- Created attachment 135596 --> https://bugs.kde.org/attachment.cgi?id=135596&action=edit Disassembly of main() when Valgrind shows the warning -- You are receiving this mail because: You are watching

[valgrind] [Bug 320546] valgrind exits with "Assertion 'in_rx' failed" for /system/lib/libva-android.so on Android 4.0.4

https://bugs.kde.org/show_bug.cgi?id=320546 Peter Klotz changed: What|Removed |Added CC||peter.klot...@gmail.com --- Comment #3 from

[valgrind] [Bug 432801] New: Valgrind 3.16.1 reports a jump based on uninitialized memory somehow related to clang and signals

https://bugs.kde.org/show_bug.cgi?id=432801 Bug ID: 432801 Summary: Valgrind 3.16.1 reports a jump based on uninitialized memory somehow related to clang and signals Product: valgrind Version: unspecified Platform: Other

[valgrind] [Bug 389412] Failed assertion in readelf.c, line 697 for clang binaries with coverage information

https://bugs.kde.org/show_bug.cgi?id=389412 Peter Klotz changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[valgrind] [Bug 389412] Failed assertion in readelf.c, line 697 for clang binaries with coverage information

https://bugs.kde.org/show_bug.cgi?id=389412 --- Comment #2 from Peter Klotz --- Hi Julian A test with the git snapshot from today showed that the assertion is still triggered (just the line number has changed): valgrind: m_debuginfo/readelf.c:715 (get_elf_symbol_info): Assertion 'in_rx&#x

[valgrind] [Bug 389412] New: Failed assertion in readelf.c, line 697 for clang binaries with coverage information

https://bugs.kde.org/show_bug.cgi?id=389412 Bug ID: 389412 Summary: Failed assertion in readelf.c, line 697 for clang binaries with coverage information Product: valgrind Version: 3.13.0 Platform: Compiled Sources

[valgrind] [Bug 384727] valgrind does not support debug info for read only segments (generated by LLD)

https://bugs.kde.org/show_bug.cgi?id=384727 Peter Klotz changed: What|Removed |Added CC||peter.klot...@gmail.com -- You are receiving