[valgrind] [Bug 383010] Add support for AVX-512 instructions

https://bugs.kde.org/show_bug.cgi?id=383010 Richard Jones changed: What|Removed |Added CC||rjo...@redhat.com -- You are receiving this

[valgrind] [Bug 455711] New: Syscall param sigaltstack(ss) points to uninitialised byte(s) when only ss.ss_flags = SS_DISABLE

https://bugs.kde.org/show_bug.cgi?id=455711 Bug ID: 455711 Summary: Syscall param sigaltstack(ss) points to uninitialised byte(s) when only ss.ss_flags = SS_DISABLE Product: valgrind Version: unspecified Platform: Other

[valgrind] [Bug 468575] Add support for RISC-V

https://bugs.kde.org/show_bug.cgi?id=468575 Richard Jones changed: What|Removed |Added CC||rjo...@redhat.com -- You are receiving this

[frameworks-kservice] [Bug 430157] KDE .desktop parser complains about files that have Type= "Application" but no Exec line, although this situation is normal.

https://bugs.kde.org/show_bug.cgi?id=430157 Richard Jones changed: What|Removed |Added CC||rjo...@redhat.com -- You are receiving this

[valgrind] [Bug 383010] Add support for AVX-512 instructions

https://bugs.kde.org/show_bug.cgi?id=383010 --- Comment #101 from Richard Jones --- (In reply to Michał Dec from comment #99) > I've just hit this bug and I can't properly work with AVX-512 instruction. I > have to scp my entire projects to a machine that doesn't use AVX

[valgrind] [Bug 468575] Add support for RISC-V

https://bugs.kde.org/show_bug.cgi?id=468575 --- Comment #48 from Richard Jones --- That'll be fine in that case! -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 468575] Add support for RISC-V

https://bugs.kde.org/show_bug.cgi?id=468575 --- Comment #45 from Richard Jones --- (In reply to Mark Wielaard from comment #35) > integer.c:132: Error: illegal operands `la zero,0' Are you maintaining these patches in a git repo somewhere? It might be easier to follow that way. I ca

[valgrind] [Bug 468575] Add support for RISC-V

https://bugs.kde.org/show_bug.cgi?id=468575 --- Comment #46 from Richard Jones --- (In reply to Mark Wielaard from comment #43) > Assuming fence and fence.tso are basically the same thing > (which they might not be) then the following seems to fix it: Normal memory model is Arm-like (ie.

[valgrind] [Bug 503419] Cannot build valgrind 3.25 on RISC-V board (Error: illegal operands `ld t0,OFFSET_riscv64_pc-2048(s0)')

https://bugs.kde.org/show_bug.cgi?id=503419 Richard Jones changed: What|Removed |Added CC||rjo...@redhat.com -- You are receiving this

[valgrind] [Bug 503253] riscv_hwprobe syscall (258) is missing

https://bugs.kde.org/show_bug.cgi?id=503253 Richard Jones changed: What|Removed |Added CC||rjo...@redhat.com -- You are receiving this

[valgrind] [Bug 361810] New: valgrind duplicate stdin after fork

https://bugs.kde.org/show_bug.cgi?id=361810 Bug ID: 361810 Summary: valgrind duplicate stdin after fork Product: valgrind Version: 3.11.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: norma

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

https://bugs.kde.org/show_bug.cgi?id=361810 --- Comment #1 from Richard Jones --- Created attachment 98409 --> https://bugs.kde.org/attachment.cgi?id=98409&action=edit forktest.sh -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

https://bugs.kde.org/show_bug.cgi?id=361810 --- Comment #3 from Richard Jones --- For reference here is the actual test that fails for us: https://github.com/libguestfs/libguestfs/blob/master/fish/test-find0.sh#L25-L30 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

https://bugs.kde.org/show_bug.cgi?id=361810 --- Comment #9 from Richard Jones --- (In reply to Tom Hughes from comment #6) > It's something in glibc doing it when __libc_freeres is run as the child > exits. > > If you add run-libc-freeres=no to the valgrind options then it