[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

[valgrind] [Bug 417993] vbit-test fail on s390x with Iop_Add32: spurious dependency on uninitialised value

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

[valgrind] [Bug 352364] ppc64: --expensive-definedness-checks=yes is not quite working here

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

[valgrind] [Bug 352364] ppc64: --expensive-definedness-checks=yes is not quite working here

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

[valgrind] [Bug 340392] Incorrect "Conditional jump..." message

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

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

https://bugs.kde.org/show_bug.cgi?id=402833 --- Comment #9 from Mark Wielaard --- Created attachment 162737 --> https://bugs.kde.org/attachment.cgi?id=162737=edit disable overlap check and test for linux-amd64 More subtle workaround patch that only disables the overlap check (and t

[valgrind] [Bug 476333] New: helgrind/tests/getaddrinfo.vgtest fails randomly

https://bugs.kde.org/show_bug.cgi?id=476333 Bug ID: 476333 Summary: helgrind/tests/getaddrinfo.vgtest fails randomly Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Linux

[valgrind] [Bug 476331] New: clean up generated/distributed filter scripts

https://bugs.kde.org/show_bug.cgi?id=476331 Bug ID: 476331 Summary: clean up generated/distributed filter scripts Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Linux

[valgrind] [Bug 417993] vbit-test fail on s390x with Iop_Add32: spurious dependency on uninitialised value

https://bugs.kde.org/show_bug.cgi?id=417993 --- Comment #12 from Mark Wielaard --- I think your analysis is correct. We already seem to do this when printing out a complaint about a real mismatch. See memcheck/tests/vbits-test/util.c (print_opnd): /* The value itself might be partially

[valgrind] [Bug 476125] Valgrind cannot read binaries containing debug symbols in DWARF 64 format

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

[valgrind] [Bug 476108] vg_replace_malloc DELETE checks size

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

[valgrind] [Bug 476108] New: vg_replace_malloc DELETE checks size

https://bugs.kde.org/show_bug.cgi?id=476108 Bug ID: 476108 Summary: vg_replace_malloc DELETE checks size Classification: Developer tools Product: valgrind Version: unspecified Platform: Other OS: Linux Status:

[valgrind] [Bug 456200] Valgrind should not require neon (simd) on armhf

https://bugs.kde.org/show_bug.cgi?id=456200 --- Comment #4 from Mark Wielaard --- I tried on an armbian 23.02.2 Buster, based on Debian 10.13, so fairly old. And with 6.1.11-rockchip, which has half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm. So

[valgrind] [Bug 456200] Valgrind should not require neon (simd) on armhf

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

[valgrind] [Bug 381819] amd64: unhandled instruction bextr (0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4) from BMI1

https://bugs.kde.org/show_bug.cgi?id=381819 --- Comment #28 from Mark Wielaard --- *** Bug 448026 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 448026] unhandled instruction bytes: 0x8F 0x6A 0x78 0x10 0xC8 0x4 0x4 0x0 0x0 0xC1

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

[valgrind] [Bug 475652] Missing suppression for __wcsncpy_avx2 (strncpy-avx2.S:308)?

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

[valgrind] [Bug 475286] Valgrind won't install (missing archives)

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

[valgrind] [Bug 461074] DWARF2 CFI reader: unhandled DW_OP_ opcode 0x11 (consts) and DW_OP_ opcode 0x92 (bregx)

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

[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.

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

[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.

https://bugs.kde.org/show_bug.cgi?id=461074 --- Comment #5 from Mark Wielaard --- Actually we have valgrind --debug-dump=frames so if you could rerun with that option and attach the output that would also be helpful. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.

https://bugs.kde.org/show_bug.cgi?id=461074 --- Comment #4 from Mark Wielaard --- Thanks, so that is in libhwy_contrib.so.1.0.7 which is https://packages.debian.org/sid/libhwy1 and can be downloaded through http://ftp.debian.org/debian/pool/main/h/highway/libhwy1_1.0.7-7_arm64.deb Without

[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.

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

[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 #53 from Mark Wielaard --- (In reply to Eyal from comment #52) > Y'all need CI, I can't even build the master branch. :-( We do have CI against various distros and arches: https://builder.sourceware.org/buildbot/#/builders?tags=valgr

[valgrind] [Bug 473745] must-be-redirected function - strlen - for valgrind 3.22 but not 3.21

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

[valgrind] [Bug 473745] must-be-redirected function - strlen - for valgrind 3.22 but not 3.21

https://bugs.kde.org/show_bug.cgi?id=473745 --- Comment #9 from Mark Wielaard --- Created attachment 161329 --> https://bugs.kde.org/attachment.cgi?id=161329=edit Explicitly load libc and any sonames that contain mandatory specs We cannot really be lazy loading glibc debugi

[valgrind] [Bug 473745] must-be-redirected function - strlen - for valgrind 3.22 but not 3.21

https://bugs.kde.org/show_bug.cgi?id=473745 --- Comment #6 from Mark Wielaard --- (In reply to Paul Floyd from comment #2) > The only thing that I can think of that could affect that is the delayed > loading of debuginfo. That might be it. If I remember correctly Debian/Ubuntu doesn'

[valgrind] [Bug 473745] must-be-redirected function - strlen - for valgrind 3.22 but not 3.21

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

[valgrind] [Bug 471807] Add support for lazy reading and downloading of DWARF debuginfo

https://bugs.kde.org/show_bug.cgi?id=471807 --- Comment #16 from Mark Wielaard --- This did create some regressions on linux-ppc64le: memcheck/tests/inlinfo (stderr) memcheck/tests/inlinfosupp (stderr) memcheck/tests/inlinfosuppobj(stderr) memcheck

[valgrind] [Bug 473687] New: Implement qDefaultExecAndArgs and qMachineId for vgdb

https://bugs.kde.org/show_bug.cgi?id=473687 Bug ID: 473687 Summary: Implement qDefaultExecAndArgs and qMachineId for vgdb Classification: Developer tools Product: valgrind Version: unspecified Platform: Other OS: Linux

[valgrind] [Bug 460951] infinite loop in ARM-64 version of instrumentation with ouptput VG_ calls at superblock and instruction level

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

[valgrind] [Bug 473604] Fix bug472219.c compile failure with Clang 16

https://bugs.kde.org/show_bug.cgi?id=473604 --- Comment #3 from Mark Wielaard --- I should have added that the proposed fix to #define _GNU_SOURCE before the #include works to get rid of the warning. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 473604] Fix bug472219.c compile failure with Clang 16

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

[valgrind] [Bug 471311] gdb --multi mode stdout redirecting to stderr

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

[valgrind] [Bug 471807] Add support for lazy reading and downloading of DWARF debuginfo

https://bugs.kde.org/show_bug.cgi?id=471807 --- Comment #15 from Mark Wielaard --- Note there was one cleanup followup for an error case: commit a0d555a0dfe078ef04ea49d991a8090ab14bd4a5 Author: Paul Floyd Date: Sat Aug 19 21:37:33 2023 +0200 Always cleanup on exit from ML_

[valgrind] [Bug 471311] gdb --multi mode stdout redirecting to stderr

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

[valgrind] [Bug 471807] Add support for lazy reading and downloading of DWARF debuginfo

https://bugs.kde.org/show_bug.cgi?id=471807 --- Comment #14 from Mark Wielaard --- I have seen no regressions from this patch. At least not in the nightly tests. There was one issue on s390x. drd/tests/getaddrinfo would randomly fail (one in ~5 times). But this can also be replicated when

[valgrind] [Bug 471807] Add support for lazy reading and downloading of DWARF debuginfo

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

[valgrind] [Bug 471807] Add support for lazy reading and downloading of DWARF debuginfo

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

[valgrind] [Bug 471807] Add support for lazy reading and downloading of DWARF debuginfo

https://bugs.kde.org/show_bug.cgi?id=471807 --- Comment #9 from Mark Wielaard --- (In reply to Aaron Merey from comment #8) > (In reply to Mark Wielaard from comment #6) > > Do we need a --enable-lazy-debuginfo=[yes|no] flag? > > Is there any advantage to the user to set it

[valgrind] [Bug 472875] New: none/tests/s390x/dfp-1 failure

https://bugs.kde.org/show_bug.cgi?id=472875 Bug ID: 472875 Summary: none/tests/s390x/dfp-1 failure Classification: Developer tools Product: valgrind Version: unspecified Platform: Other OS: Linux Status:

[valgrind] [Bug 472512] Remove Stack and Global Blocks from debuginfo handling.

https://bugs.kde.org/show_bug.cgi?id=472512 Mark Wielaard changed: What|Removed |Added CC||ame...@redhat.com Status|REPORTED

[valgrind] [Bug 472512] New: Remove Stack and Global Blocks from debuginfo handling.

https://bugs.kde.org/show_bug.cgi?id=472512 Bug ID: 472512 Summary: Remove Stack and Global Blocks from debuginfo handling. Classification: Developer tools Product: valgrind Version: 3.21.0 Platform: Other

[valgrind] [Bug 471807] Add support for lazy reading and downloading of DWARF debuginfo

https://bugs.kde.org/show_bug.cgi?id=471807 --- Comment #7 from Mark Wielaard --- v3 does work. But I admit to not fully understand why/how. The addr_load_di calls in coregrind/m_stacktrace..c seems unnecessary (you can comment them out and things still work fine). This is because

[valgrind] [Bug 471807] Add support for lazy reading and downloading of DWARF debuginfo

https://bugs.kde.org/show_bug.cgi?id=471807 --- Comment #6 from Mark Wielaard --- Do we need a --enable-lazy-debuginfo=[yes|no] flag? Is there any advantage to the user to set it to no? Less variants in the code seems good. -- You are receiving this mail because: You are watching all bug

[valgrind] [Bug 472402] memcheck "make tests" build fails: filter_sized_delete missing

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

[valgrind] [Bug 471807] Add support for lazy reading and downloading of DWARF debuginfo

https://bugs.kde.org/show_bug.cgi?id=471807 --- Comment #4 from Mark Wielaard --- (In reply to Aaron Merey from comment #3) > Created attachment 160259 [details] > patch-v2 > > I've updated the patch with lazy debuginfo support for all ELF platforms. I > regression tested th

[valgrind] [Bug 471807] Add support for lazy reading and downloading of DWARF debuginfo

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

[valgrind] [Bug 470132] s390x: Assertion failure on VGM instruction

https://bugs.kde.org/show_bug.cgi?id=470132 --- Comment #5 from Mark Wielaard --- Note that the lfedora1 machine (now at Fedora 38) is showing this issue too now: https://sourceforge.net/p/valgrind/mailman/message/37865251/ -- You are receiving this mail because: You are watching all bug

[valgrind] [Bug 470132] s390x: Assertion failure on VGM instruction

https://bugs.kde.org/show_bug.cgi?id=470132 --- Comment #4 from Mark Wielaard --- I also backported this to the fedora valgrind package. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f4019f53e1 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 460192] Add epoll_pwait2

https://bugs.kde.org/show_bug.cgi?id=460192 Mark Wielaard changed: What|Removed |Added CC||ronnebaumfinan...@gmail.com --- Comment #3

[valgrind] [Bug 471476] unhandled amd64-linux syscall: 441

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

[valgrind] [Bug 471311] New: gdb --multi mode stdout redirecting to stderr

https://bugs.kde.org/show_bug.cgi?id=471311 Bug ID: 471311 Summary: gdb --multi mode stdout redirecting to stderr Classification: Developer tools Product: valgrind Version: 3.21.0 Platform: Other OS: Linux

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

https://bugs.kde.org/show_bug.cgi?id=471222 Bug ID: 471222 Summary: support tracking of file descriptors being double closed Classification: Developer tools Product: valgrind Version: unspecified Platform: Other

[valgrind] [Bug 470132] s390x: Assertion failure on VGM instruction

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

[valgrind] [Bug 470978] s390x: Valgrind cannot start qemu-kvm when "sysctl vm.allocate_pgste=0"

https://bugs.kde.org/show_bug.cgi?id=470978 --- Comment #4 from Mark Wielaard --- The new configure check and tool ldflags addition look good to me. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 470830] Don't print actions vgdb me ... continue for vgdb --multi mode

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

[valgrind] [Bug 471032] s390x: helgrind/tests/tc11_XCHG.c expects code to be at a low address space

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

[valgrind] [Bug 471032] s390x: helgrind/tests/tc11_XCHG.c expects code to be at a low address space

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

[valgrind] [Bug 470978] s390x: Valgrind cannot start qemu-kvm when "sysctl vm.allocate_pgste=0"

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

[valgrind] [Bug 470830] New: Don't print actions vgdb me ... continue for vgdb --multi mode

https://bugs.kde.org/show_bug.cgi?id=470830 Bug ID: 470830 Summary: Don't print actions vgdb me ... continue for vgdb --multi mode Classification: Developer tools Product: valgrind Version: 3.21.0 Platform: Other

[valgrind] [Bug 470520] Multiple realloc zero errors crash in MC_(eq_Error)

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

[valgrind] [Bug 470520] Multiple realloc zero errors crash in MC_(eq_Error)

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

[valgrind] [Bug 470520] New: Multiple realloc zero errors crash in MC_(eq_Error)

https://bugs.kde.org/show_bug.cgi?id=470520 Bug ID: 470520 Summary: Multiple realloc zero errors crash in MC_(eq_Error) Classification: Developer tools Product: valgrind Version: 3.21.0 Platform: Other OS: Linux

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

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

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

https://bugs.kde.org/show_bug.cgi?id=402833 --- Comment #8 from Mark Wielaard --- The "workaround from comment #6 isn't complete since memmove_chk and memcpy_chk can also alias possibly causing memmove_chk doing an overlap check (because it gets confused with memcpy_chk). So the current

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

https://bugs.kde.org/show_bug.cgi?id=402833 Mark Wielaard changed: What|Removed |Added CC||mli...@suse.cz --- Comment #7 from Mark

[valgrind] [Bug 453084] Misleading error with memmove: Source and destination overlap in memcpy_chk

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

[valgrind] [Bug 470260] Valgrind crashes when run with --multi

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

[valgrind] [Bug 469768] Make it possible to install gdb scripts in a different location

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

[valgrind] [Bug 469768] Make it possible to install gdb scripts in a different location

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

[valgrind] [Bug 460192] Add epoll_pwait2

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

[valgrind] [Bug 469768] Make it possible to install gdb scripts in a different location

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

[valgrind] [Bug 469768] Make it possible to install gdb scripts in a different location

https://bugs.kde.org/show_bug.cgi?id=469768 --- Comment #1 from Mark Wielaard --- e.g. for fedora this would be used with configure --with-gdbscripts-dir=%{_datadir}/gdb/auto-load -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 460192] Add epoll_pwait2

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

[valgrind] [Bug 469768] New: Make it possible to install gdb scripts in a different location

https://bugs.kde.org/show_bug.cgi?id=469768 Bug ID: 469768 Summary: Make it possible to install gdb scripts in a different location Classification: Developer tools Product: valgrind Version: 3.20.0 Platform: Other

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

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

[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

https://bugs.kde.org/show_bug.cgi?id=469049 --- Comment #6 from Mark Wielaard --- (In reply to Paul Floyd from comment #5) > This is an LTO issue. On gccfarm gcc203 which is > > paulf@gcc203:~/scratch/valgrind$ lscpu > Architecture:ppc64 > CPU op-mode(s):

[valgrind] [Bug 469097] ppc64(be) doesn't support SCV syscall instruction

https://bugs.kde.org/show_bug.cgi?id=469097 --- Comment #4 from Mark Wielaard --- commit b4ec6a6ff767098714ffa8c4e3e3081d98fd2d66 (HEAD -> master) Author: Mark Wielaard Date: Fri Apr 28 13:34:48 2023 +0200 Support SCV_FLAG also on VGP_ppc64be_linux Running on a kernel that suppo

[valgrind] [Bug 469097] ppc64(be) doesn't support SCV syscall instruction

https://bugs.kde.org/show_bug.cgi?id=469097 --- Comment #3 from Mark Wielaard --- With filtering out PPC_FEATURE2_SCV the regtest results look much more reasonable: == 706 tests, 7 stderr failures, 3 stdout failures, 0 stderrB failures, 2 stdoutB failures, 2 post failures == gdbserver_tests

[valgrind] [Bug 469097] ppc64(be) doesn't support SCV syscall instruction

https://bugs.kde.org/show_bug.cgi?id=469097 --- Comment #2 from Mark Wielaard --- Just disabling the assert does get most things working, but there were some hangs and various failing regtests == 706 tests, 38 stderr failures, 10 stdout failures, 0 stderrB failures, 0 stdoutB failures, 2 post

[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

https://bugs.kde.org/show_bug.cgi?id=469049 --- Comment #4 from Mark Wielaard --- (In reply to Paul Floyd from comment #2) > (In reply to Mark Wielaard from comment #1) > > There is a debian ppc64(be) system for builder.sourceware.org which builds: > > https://builder.sourcewa

[valgrind] [Bug 469097] ppc64(be) doesn't support SCV syscall instruction

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

[valgrind] [Bug 469097] New: ppc64(be) doesn't support SCV syscall instruction

https://bugs.kde.org/show_bug.cgi?id=469097 Bug ID: 469097 Summary: ppc64(be) doesn't support SCV syscall instruction Classification: Developer tools Product: valgrind Version: 3.20.0 Platform: Other OS: Linux

[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

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

[valgrind] [Bug 464103] Enhancement: add a client request to DHAT to mark memory to be histogrammed

https://bugs.kde.org/show_bug.cgi?id=464103 --- Comment #6 from Mark Wielaard --- user_histo1.stdout.exp is missing from EXTRA_DIST, but that is easy to fix On my local system the test however fails --- user_histo1.stderr.exp 2023-04-21 22:33:09.538844963 +0200 +++ user_histo1.stderr.out

[valgrind] [Bug 464103] Enhancement: add a client request to DHAT to mark memory to be histogrammed

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

[valgrind] [Bug 436413] Warn about realloc of size zero

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

[valgrind] [Bug 397083] Likely false positive "uninitialised value(s)" for __wmemchr_avx2 and __wmemcmp_avx2_movbe

https://bugs.kde.org/show_bug.cgi?id=397083 --- Comment #12 from Mark Wielaard --- (In reply to Mark Wielaard from comment #11) > It looks like the original c++ issue (which called down to glibc wmemchr) > has been fixed by bug #388862 in 3.14.0 (the reporter used 3.13.0). I think

[valgrind] [Bug 397083] Likely false positive "uninitialised value(s)" for __wmemchr_avx2 and __wmemcmp_avx2_movbe

https://bugs.kde.org/show_bug.cgi?id=397083 --- Comment #11 from Mark Wielaard --- It looks like the original c++ issue (which called down to glibc wmemchr) has been fixed by bug #388862 in 3.14.0 (the reporter used 3.13.0). I think just intercepting the generic wmemchr (ifunc) is enough, you

[valgrind] [Bug 397083] Likely false positive "uninitialised value(s)" for __wmemchr_avx2 and __wmemcmp_avx2_movbe

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

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

https://bugs.kde.org/show_bug.cgi?id=383010 Mark Wielaard changed: What|Removed |Added CC||rincebr...@gmail.com --- Comment #87 from Mark

<    1   2   3   4   5   6   7   8   9   10   >