[valgrind] [Bug 486180] [Valgrind][MIPS] 'VexGuestArchState' has no member named 'guest_IP_AT_SYSCALL'

https://bugs.kde.org/show_bug.cgi?id=486180 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Status|REPORTED

[valgrind] [Bug 362680] --error-exitcode not honored when file descriptor leaks are found

https://bugs.kde.org/show_bug.cgi?id=362680 Mark Wielaard changed: What|Removed |Added CC||v...@altlinux.org --- Comment #6 from Mark

[valgrind] [Bug 482358] Feature Request: Add --track-fds=error

https://bugs.kde.org/show_bug.cgi?id=482358 Mark Wielaard changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED

[valgrind] [Bug 485924] No support for pidfd_send_signal system call

https://bugs.kde.org/show_bug.cgi?id=485924 --- Comment #3 from Mark Wielaard --- So the only tricky part is that we want to mimic this part of the (generic) PRE(sys_kill): /* If we're sending SIGKILL, check to see if the target is one of our threads and handle it specially

[valgrind] [Bug 485924] No support for pidfd_send_signal system call

https://bugs.kde.org/show_bug.cgi?id=485924 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[valgrind] [Bug 485778] Crash with --track-fds=all and --gen-suppressions=all

https://bugs.kde.org/show_bug.cgi?id=485778 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED

[valgrind] [Bug 485778] Crash with --track-fds=all and --gen-suppressions=all

https://bugs.kde.org/show_bug.cgi?id=485778 Mark Wielaard changed: What|Removed |Added Attachment #168679|0 |1 is obsolete

[valgrind] [Bug 485778] Crash with --track-fds=all and --gen-suppressions=all

https://bugs.kde.org/show_bug.cgi?id=485778 --- Comment #2 from Mark Wielaard --- Created attachment 168679 --> https://bugs.kde.org/attachment.cgi?id=168679=edit core errors gensuppressions support Initial implementation for --gen-suppressions support for core errors With this the testc

[valgrind] [Bug 485778] Crash with --track-fds=all and --gen-suppressions=all

https://bugs.kde.org/show_bug.cgi?id=485778 Mark Wielaard changed: What|Removed |Added Assignee|jsew...@acm.org |m...@klomp.org Status|REPORTED

[valgrind] [Bug 328563] make track-fds support xml output

https://bugs.kde.org/show_bug.cgi?id=328563 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED

[valgrind] [Bug 362680] --error-exitcode not honored when file descriptor leaks are found

https://bugs.kde.org/show_bug.cgi?id=362680 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution

[valgrind] [Bug 362680] --error-exitcode not honored when file descriptor leaks are found

https://bugs.kde.org/show_bug.cgi?id=362680 --- Comment #4 from Mark Wielaard --- bug #328563 has an attachment that implements this -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 450705] s390x: Add NNPA support (arch14)

https://bugs.kde.org/show_bug.cgi?id=450705 --- Comment #8 from Mark Wielaard --- (In reply to Andreas Arnez from comment #7) > (In reply to Andreas Arnez from comment #6) > > Created attachment 168623 [details] > > Updated version of the extension proposal > I pushed this now

[valgrind] [Bug 450705] s390x: Add NNPA support (arch14)

https://bugs.kde.org/show_bug.cgi?id=450705 --- Comment #5 from Mark Wielaard --- I haven't reviewed the fully proposal, but in general I like the idea of using the same mechanism as the syscalls for instrumenting these more complex instructions. It is at least familiar. You might want to rename

[valgrind] [Bug 450705] s390x: Add NNPA support (arch14)

https://bugs.kde.org/show_bug.cgi?id=450705 --- Comment #3 from Mark Wielaard --- Extension idea was posted to the mailinglist: https://sourceforge.net/p/valgrind/mailman/message/58753610/ -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 485276] std::optional use: "Conditional jump or move depends on uninitialised value(s)" (clang) aarch64

https://bugs.kde.org/show_bug.cgi?id=485276 --- Comment #4 from Mark Wielaard --- (In reply to Mark Wielaard from comment #3) > I am unable to replicate this with either clang version 17.0.6 or 18.1.2, > not with -O2 or -O1. On x86_64. Missed that the original report was against arm64

[valgrind] [Bug 485276] std::optional use: "Conditional jump or move depends on uninitialised value(s)" (clang) aarch64

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

[valgrind] [Bug 472329] std::optional use: "Conditional jump or move depends on uninitialised value(s)" (g++)

https://bugs.kde.org/show_bug.cgi?id=472329 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 CC

[valgrind] [Bug 481874] Add arm64 support for FreeBSD

https://bugs.kde.org/show_bug.cgi?id=481874 --- Comment #17 from Mark Wielaard --- .git-blame-ignore-revs references a clang-format rev that doesn't exist in tree. Makefile.all.am and Makefile.tool.am look correct. NEWS OK. VEX changes OK, except for unnecessarily extending VexGuestARM64State

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

https://bugs.kde.org/show_bug.cgi?id=485487 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

https://bugs.kde.org/show_bug.cgi?id=485487 --- Comment #7 from Mark Wielaard --- There is now also an fedora eln build: https://koji.fedoraproject.org/koji/buildinfo?buildID=2437715 Since eln is build with -march=x86-64-v3 this might be a good testing environment. Please let me know if you

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

https://bugs.kde.org/show_bug.cgi?id=485487 --- Comment #6 from Mark Wielaard --- (In reply to Mark Wielaard from comment #5) > I'll add it to the next fedora rawhide valgrind build so we can test it a > bit more. There is now valgrind-3.22.0-8.fc41 with this and some other (x86-64-v3)

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

https://bugs.kde.org/show_bug.cgi?id=485487 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

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

[valgrind] [Bug 463458] memcheck/tests/vcpu_fnfns fails when glibc is built for x86-64-v3 target

https://bugs.kde.org/show_bug.cgi?id=463458 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[valgrind] [Bug 463463] none/tests/amd64/fma fails when executed under valgrind on a x86-64-v3 system

https://bugs.kde.org/show_bug.cgi?id=463463 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[valgrind] [Bug 481127] [PATCH] amd64: Implement VFMADD213 for Iop_MAddF32

https://bugs.kde.org/show_bug.cgi?id=481127 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution

[valgrind] [Bug 481127] [PATCH] amd64: Implement VFMADD213 for Iop_MAddF32

https://bugs.kde.org/show_bug.cgi?id=481127 --- Comment #10 from Mark Wielaard --- Created attachment 168440 --> https://bugs.kde.org/attachment.cgi?id=168440=edit valgrind.fma_arm64.diff This is the variant of the patch that I tested. It looks good to me. How should we credit this w

[valgrind] [Bug 481127] [PATCH] amd64: Implement VFMADD213 for Iop_MAddF32

https://bugs.kde.org/show_bug.cgi?id=481127 Mark Wielaard changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0

[valgrind] [Bug 463458] memcheck/tests/vcpu_fnfns fails when glibc is built for x86-64-v3 target

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

[valgrind] [Bug 463456] memcheck/tests/origin6-fp fails when building for x86-64-v3 target

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

[valgrind] [Bug 463463] none/tests/amd64/fma fails when executed under valgrind on a x86-64-v3 system

https://bugs.kde.org/show_bug.cgi?id=463463 --- Comment #2 from Mark Wielaard --- These seem rounding issues, fixed by https://bugs.kde.org/show_bug.cgi?id=481127 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 463463] none/tests/amd64/fma fails when executed under valgrind on a x86-64-v3 system

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

[valgrind] [Bug 377966] arm64 unhandled instruction dc zva

https://bugs.kde.org/show_bug.cgi?id=377966 Mark Wielaard changed: What|Removed |Added Summary|Error message said to |arm64 unhandled instruction

[valgrind] [Bug 479600] Segmentation fault launching the valgrind (mipsel-openwrt-linux-musl-gcc)

https://bugs.kde.org/show_bug.cgi?id=479600 Mark Wielaard changed: What|Removed |Added Summary|Segmentation fault |Segmentation fault

[valgrind] [Bug 481874] Add arm64 support for FreeBSD

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

[valgrind] [Bug 484426] aarch64: 0.5 gets rounded to 0

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

[valgrind] [Bug 484002] Add suppression for invalid read in glibc's __wcpncpy_avx2() via wcsxfrm()

https://bugs.kde.org/show_bug.cgi?id=484002 --- Comment #5 from Mark Wielaard --- Comment on attachment 167483 --> https://bugs.kde.org/attachment.cgi?id=167483 first attempt at a patch Very nice. Before the patch: $ ~/src/valgrind/vg-in-place ./t ==66177== Memcheck, a memory error detec

[valgrind] [Bug 484002] Add suppression for invalid read in glibc's __wcpncpy_avx2() via wcsxfrm()

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

[valgrind] [Bug 483711] -m32 flag breaks Valgrind

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

[valgrind] [Bug 471222] support tracking of file descriptors being double closed

https://bugs.kde.org/show_bug.cgi?id=471222 Mark Wielaard changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution

[valgrind] [Bug 471222] support tracking of file descriptors being double closed

https://bugs.kde.org/show_bug.cgi?id=471222 --- Comment #17 from Mark Wielaard --- (In reply to Paul Floyd from comment #14) > On second thoughts, isn't the fdleak_ipv4 double close message expected? Yes, it is. It also failed for me locally. I added it to the none/tests/fdleak_ipv4.stderr.

[valgrind] [Bug 471222] support tracking of file descriptors being double closed

https://bugs.kde.org/show_bug.cgi?id=471222 --- Comment #16 from Mark Wielaard --- (In reply to Paul Floyd from comment #13) > I had to modify double_close_range.c and socket_close.c like this > > #if defined(__linux__) > #include > #endif > > I get 3 new failures >

[valgrind] [Bug 471222] support tracking of file descriptors being double closed

https://bugs.kde.org/show_bug.cgi?id=471222 --- Comment #15 from Mark Wielaard --- I needed the following on a system that didn't have close_range: diff --git a/none/tests/Makefile.am b/none/tests/Makefile.am index f56eb7faab67..a37bb27257a6 100644 --- a/none/tests/Makefile.am +++ b/none/tests

[valgrind] [Bug 482358] Feature Request: Add --track-fds=error

https://bugs.kde.org/show_bug.cgi?id=482358 --- Comment #2 from Mark Wielaard --- See also https://bugs.kde.org/show_bug.cgi?id=362680 which contains a description how to resurrect CoreErrors (but no patch yet?) -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 482358] Feature Request: Add --track-fds=error

https://bugs.kde.org/show_bug.cgi?id=482358 Mark Wielaard changed: What|Removed |Added CC||ahajk...@redhat.com

[valgrind] [Bug 471222] support tracking of file descriptors being double closed

https://bugs.kde.org/show_bug.cgi?id=471222 --- Comment #8 from Mark Wielaard --- BTW. In that testcase memcheck/tests/freebsd/close_range.c it has: /* It looks like close_range was initially implemented for FreeBSD 13 * but without CLOSE_RANGE_CLOEXEC * That implementation got back ported

[valgrind] [Bug 471222] support tracking of file descriptors being double closed

https://bugs.kde.org/show_bug.cgi?id=471222 --- Comment #7 from Mark Wielaard --- I forgot about freebsd, sorry. But I see the close_range wrappers are almost identical, so that is good. We can adapt them together. And freebsd already has ./memcheck/tests/freebsd/close_range.vgtest Lets see

[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)

https://bugs.kde.org/show_bug.cgi?id=478624 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Resolution

[valgrind] [Bug 480126] Build failure on Raspberry Pi 5 / OS 6.1.0-rpi7-rpi-v8

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

[valgrind] [Bug 331311] Valgrind shows open files in /proc/self/fd that don't work for the process

https://bugs.kde.org/show_bug.cgi?id=331311 Mark Wielaard changed: What|Removed |Added CC||ahajk...@redhat.com

[valgrind] [Bug 362680] --error-exitcode not honored when file descriptor leaks are found

https://bugs.kde.org/show_bug.cgi?id=362680 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org -- You are receiving this mail

[valgrind] [Bug 337388] fcntl works on Valgrind's own file descriptors

https://bugs.kde.org/show_bug.cgi?id=337388 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 CC

[valgrind] [Bug 162848] --log-file output isn't split when a program forks

https://bugs.kde.org/show_bug.cgi?id=162848 Mark Wielaard changed: What|Removed |Added CC||borntrae...@de.ibm.com --- Comment #24 from

[valgrind] [Bug 253308] --log-file and --xml-file dont work well with --trace-children=yes

https://bugs.kde.org/show_bug.cgi?id=253308 Mark Wielaard changed: What|Removed |Added Resolution|--- |DUPLICATE CC

[valgrind] [Bug 471222] support tracking of file descriptors being double closed

https://bugs.kde.org/show_bug.cgi?id=471222 Mark Wielaard changed: What|Removed |Added CC||ahajk...@redhat.com

[valgrind] [Bug 202770] open fd at exit --log-socket=127.0.0.1:1500 with --track-fds=yes and --trace-children=yes with a program that calls fork then exec

https://bugs.kde.org/show_bug.cgi?id=202770 Mark Wielaard changed: What|Removed |Added CC||ahajk...@redhat.com

[valgrind] [Bug 311655] --log-file=FILE leads to apparent fd leak ("Open file descriptor 3: $LOGFILE")

https://bugs.kde.org/show_bug.cgi?id=311655 Mark Wielaard changed: What|Removed |Added CC||ahajk...@redhat.com

[valgrind] [Bug 479661] Valgrind leaks file descriptors

https://bugs.kde.org/show_bug.cgi?id=479661 Mark Wielaard changed: What|Removed |Added CC||ahajk...@redhat.com

[valgrind] [Bug 477992] compiler generated overlapping memcpy diagnosed

https://bugs.kde.org/show_bug.cgi?id=477992 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[valgrind] [Bug 477198] Add fchmodat2 syscall on linux

https://bugs.kde.org/show_bug.cgi?id=477198 --- Comment #3 from Mark Wielaard --- Also added to the VALGRIND_3_22_BRANCH as: commit a43e62dddcf51ec6578a90c5988a41e856b44b05 (HEAD -> VALGRIND_3_22_BRANCH) Author: Mark Wielaard Date: Sat Nov 18 21:17:02 2023 +0100 Add fchmodat2 sysc

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

https://bugs.kde.org/show_bug.cgi?id=476465 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[valgrind] [Bug 478211] Redundant code for vgdb.c and Valgrind core tools

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

[valgrind] [Bug 476548] valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold

https://bugs.kde.org/show_bug.cgi?id=476548 --- Comment #9 from Mark Wielaard --- Also pushed to VALGRIND_3_22_BRANCH as: commit 1d00e5ce0fb069911c4b525ec38289fb5d9021b0 Author: Paul Floyd Date: Sat Nov 18 08:49:34 2023 +0100 Bug 476548 - valgrind 3.22.0 fails on assertion when loading

[valgrind] [Bug 476548] valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold

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

[valgrind] [Bug 477198] Add fchmodat2 syscall on linux

https://bugs.kde.org/show_bug.cgi?id=477198 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED

[valgrind] [Bug 477719] vgdb incorrectly replies to qRcmd packet

https://bugs.kde.org/show_bug.cgi?id=477719 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED CC

[valgrind] [Bug 281059] Cannot connect to Oracle using valgrind

https://bugs.kde.org/show_bug.cgi?id=281059 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[valgrind] [Bug 237920] valgrind segfault on fork failure

https://bugs.kde.org/show_bug.cgi?id=237920 Mark Wielaard changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|CONFIRMED

[valgrind] [Bug 328563] make track-fds support xml output

https://bugs.kde.org/show_bug.cgi?id=328563 Mark Wielaard changed: What|Removed |Added Attachment #127438|0 |1 is obsolete

[valgrind] [Bug 477198] Add fchmodat2 syscall on linux

https://bugs.kde.org/show_bug.cgi?id=477198 Mark Wielaard changed: What|Removed |Added Assignee|jsew...@acm.org |m...@klomp.org Ever confirmed|0

[valgrind] [Bug 477198] New: Add fchmodat2 syscall on linux

https://bugs.kde.org/show_bug.cgi?id=477198 Bug ID: 477198 Summary: Add fchmodat2 syscall on linux Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Linux Status: REPORTED

[valgrind] [Bug 476708] valgrind-monitor.py regular expressions should use raw strings

https://bugs.kde.org/show_bug.cgi?id=476708 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[valgrind] [Bug 476708] valgrind-monitor.py regular expressions should use raw strings

https://bugs.kde.org/show_bug.cgi?id=476708 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Assignee|jsew...@acm.org

[valgrind] [Bug 253383] [PATCH] several LTP testcases trigger VALGRIND INTERNAL ERROR

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

[valgrind] [Bug 200829] Ptrcheck doesn't work on Mac OS X

https://bugs.kde.org/show_bug.cgi?id=200829 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution

[valgrind] [Bug 206618] ptrcheck complains about things allocated with alloca

https://bugs.kde.org/show_bug.cgi?id=206618 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC

[valgrind] [Bug 308027] Warning: negative range in .debug_loc section

https://bugs.kde.org/show_bug.cgi?id=308027 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED CC

[valgrind] [Bug 306340] parse_var_DIE confused by DWARF from clang-3.1

https://bugs.kde.org/show_bug.cgi?id=306340 Mark Wielaard changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED

[valgrind] [Bug 266045] Slackware 10.2 make fails

https://bugs.kde.org/show_bug.cgi?id=266045 Mark Wielaard changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC

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

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

[valgrind] [Bug 345414] Missing seccomp support (WARNING: unhandled syscall: 317)

https://bugs.kde.org/show_bug.cgi?id=345414 Mark Wielaard changed: What|Removed |Added See Also||https://bugzilla.mozilla.or

[valgrind] [Bug 471340] callgrind Error: can not open cache simulation output file callgrind.out.pid

https://bugs.kde.org/show_bug.cgi?id=471340 Mark Wielaard changed: What|Removed |Added See Also||https://bugs.kde.org/show_b

[valgrind] [Bug 345414] Missing seccomp support (WARNING: unhandled syscall: 317)

https://bugs.kde.org/show_bug.cgi?id=345414 Mark Wielaard changed: What|Removed |Added See Also||https://bugs.kde.org/show_b

[valgrind] [Bug 380183] WARNING: unhandled amd64-linux syscall: 317 (seccomp)

https://bugs.kde.org/show_bug.cgi?id=380183 Mark Wielaard changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED

[valgrind] [Bug 345414] Missing seccomp support (WARNING: unhandled syscall: 317)

https://bugs.kde.org/show_bug.cgi?id=345414 Mark Wielaard changed: What|Removed |Added CC||toralf.foers...@gmx.de --- Comment #16 from

[valgrind] [Bug 345414] Missing seccomp support (WARNING: unhandled syscall: 317)

https://bugs.kde.org/show_bug.cgi?id=345414 --- Comment #15 from Mark Wielaard --- Also note this patch that implements more of seccomp: https://sourceforge.net/p/valgrind/mailman/message/46305485/ -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 476978] [SSE4.1] missing support for PMAXUD (x86)

https://bugs.kde.org/show_bug.cgi?id=476978 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Summary|[SSE4.1

[valgrind] [Bug 401284] False positive "Source and destination overlap in strncat"

https://bugs.kde.org/show_bug.cgi?id=401284 --- Comment #11 from Mark Wielaard --- (In reply to Paul Floyd from comment #9) > > src_orig, \ > > (Addr)dst-(Addr)dst_orig+1, \ > > - (Addr)sr

[valgrind] [Bug 460616] disInstr(arm64): unhandled instruction 0x4E819402 (dotprod/ASIMDDP)

https://bugs.kde.org/show_bug.cgi?id=460616 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution

[valgrind] [Bug 460616] disInstr(arm64): unhandled instruction 0x4E819402 (dotprod/ASIMDDP)

https://bugs.kde.org/show_bug.cgi?id=460616 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Status|REPORTED

[valgrind] [Bug 401284] False positive "Source and destination overlap in strncat"

https://bugs.kde.org/show_bug.cgi?id=401284 --- Comment #4 from Mark Wielaard --- (In reply to AL from comment #3) > My point was that strncat() will never even encounter the terminating '\0' > byte in the source string because its counter (5) will be depleted to 0 &g

[valgrind] [Bug 401284] False positive "Source and destination overlap in strncat"

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

[valgrind] [Bug 463859] valgrind hangs and is totally unresponsive running a very "simple" Rust program that uses glommio

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

[valgrind] [Bug 444224] Missing io_uring syscall

https://bugs.kde.org/show_bug.cgi?id=444224 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[valgrind] [Bug 476662] vex amd64->IR: unhandled instruction bytes: 0x66 0x9D (popf)

https://bugs.kde.org/show_bug.cgi?id=476662 --- Comment #2 from Mark Wielaard --- Is this only an issue with this hand assembly? It would be interesting to see real code that uses this. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 476708] New: valgrind-monitor.py regular expressions should use raw strings

https://bugs.kde.org/show_bug.cgi?id=476708 Bug ID: 476708 Summary: valgrind-monitor.py regular expressions should use raw strings Classification: Developer tools Product: valgrind Version: unspecified Platform: Other

[valgrind] [Bug 476662] vex amd64->IR: unhandled instruction bytes: 0x66 0x9D (popf)

https://bugs.kde.org/show_bug.cgi?id=476662 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Ever confirmed|0

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

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

[valgrind] [Bug 402833] memcheck/tests/overlap testcase fails, memcpy seen as memmove

https://bugs.kde.org/show_bug.cgi?id=402833 --- Comment #10 from Mark Wielaard --- (In reply to Mark Wielaard from comment #9) > Created attachment 162737 [details] > disable overlap check and test for linux-amd64 > > More subtle workaround patch that only disables the overlap che

  1   2   3   4   5   6   7   8   9   10   >