1 Release 3.23.0 (?? Apr 2024)
2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
4 This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux,
5 PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux,
6 MIPS64/Linux, ARM/Android, ARM64/Android, MIPS32/Android, X86/Android,
7 X86/Solaris, AMD64/Solaris, AMD64/MacOSX 10.12, X86/FreeBSD and
8 AMD64/FreeBSD. There is also preliminary support for X86/macOS 10.13,
9 AMD64/macOS 10.13 and nanoMIPS/Linux.
11 * ==================== CORE CHANGES ===================
13 * ================== PLATFORM CHANGES =================
15 * ==================== TOOL CHANGES ===================
17 * ==================== FIXED BUGS ====================
19 The following bugs have been fixed or resolved. Note that "n-i-bz"
20 stands for "not in bugzilla" -- that is, a bug that was reported to us
21 but never got a bugzilla entry. We encourage you to file bugs in
22 bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather
23 than mailing the developers (or mailing lists) directly -- bugs that
24 are not entered into bugzilla tend to get forgotten about or ignored.
27 283429 ARM leak checking needs CLEAR_CALLER_SAVED_REGS
28 281059 Cannot connect to Oracle using valgrind
29 390269 unhandled amd64-darwin syscall: unix:464 (openat_nocancel)
30 401284 False positive "Source and destination overlap in strncat"
31 428364 Signals inside io_uring_enter not handled
32 437790 valgrind reports "Conditional jump or move depends on uninitialised
33 value" in memchr of macOS 10.12-10.15
34 460616 disInstr(arm64): unhandled instruction 0x4E819402 (dotprod/ASIMDDP)
35 466762 Add redirs for C23 free_sized() and free_aligned_sized()
36 466884 Missing writev uninit padding suppression for _XSend
37 471036 disInstr_AMD64: disInstr miscalculated next %rip on RORX imm8, m32/64, r32/6
38 475498 Add reallocarray wrapper
39 476320 Build failure with GCC
40 476331 clean up generated/distributed filter scripts
41 476535 Difference in allocation size for massif/tests/overloaded-new between
42 clang++/libc++ and g++/libstdc++
43 476548 valgrind 3.22.0 fails on assertion when loading debuginfo file
45 476708 valgrind-monitor.py regular expressions should use raw strings
46 476780 Extend strlcat and strlcpy wrappers to GNU libc
47 476787 Build of Valgrind 3.21.0 fails when SOLARIS_PT_SUNDWTRACE_THRP is
49 476887 WARNING: unhandled amd64-freebsd syscall: 578
50 477198 Add fchmodat2 syscall on linux
51 477628 Add mremap support for Solaris
52 477630 Include ucontext.h rather than sys/ucontext.h in Solaris sources
53 477719 vgdb incorrectly replies to qRcmd packet
54 478211 Redundant code for vgdb.c and Valgrind core tools
55 478624 Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns
56 (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26
57 478837 valgrind fails to read debug info for rust binaries
58 479041 Executables without RW sections do not trigger debuginfo reading
59 480052 WARNING: unhandled amd64-freebsd syscall: 580
60 480126 Build failure on Raspberry Pi 5 / OS 6.1.0-rpi7-rpi-v8
61 480405 valgrind 3.22.0 "m_debuginfo/image.c:586 (set_CEnt):
62 Assertion '!sr_isError(sr)' failed."
63 480488 Add support for FreeBSD 13.3
64 480706 Unhandled syscall 325 (mlock2)
65 481131 [PATCH] x86 regtest: fix clobber lists in generated asm statements
66 n-i-bz Add redirect for memccpy
68 To see details of a given bug, visit
69 https://bugs.kde.org/show_bug.cgi?id=XXXXXX
70 where XXXXXX is the bug number as listed above.
72 (3.23.0.RC1: ?? Apr 2024)
74 Release 3.22.0 (31 Oct 2023)
75 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
77 This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux,
78 PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux,
79 MIPS64/Linux, ARM/Android, ARM64/Android, MIPS32/Android, X86/Android,
80 X86/Solaris, AMD64/Solaris, AMD64/MacOSX 10.12, X86/FreeBSD and
81 AMD64/FreeBSD. There is also preliminary support for X86/macOS 10.13,
82 AMD64/macOS 10.13 and nanoMIPS/Linux.
84 * ==================== CORE CHANGES ===================
86 * A new configure option --with-gdbscripts-dir lets you install
87 the gdb valgrind python monitor scripts in a specific location.
88 For example a distro could use it to install the scripts in a
89 safe load location --with-gdbscripts-dir=%{_datadir}/gdb/auto-load
90 It is also possible to configure --without-gdb-scripts-dir so no
91 .debug_gdb_scripts section is added to the vgpreload library and
92 no valgrind-monitor python scripts are installed at all.
94 * ================== PLATFORM CHANGES =================
96 * Support has been added for FreeBSD 14 and FreeBSD 15.
97 * Add support for the folllowing FreeBSD system calls:
98 close_range, kqueuex, membarrier, timerfd_create,
99 timerfd_settime and timerfd_gettime (all added in FreeBSD 15).
101 * ==================== TOOL CHANGES ===================
103 * Memcheck now tests and warns about the values used for
104 alignment and size. These apply to various functions: memalign,
105 posix_memalign and aligned_alloc in C and various overloads
106 of operators new and delete in C++. The kinds of error that can
108 - invalid alignment, for instance the alignment is usually required
110 - mismatched alignment between aligned allocation and aligned
112 - mismatched size when sized delete is used
113 - bad size for functions that have implementation defined behaviour
114 when the requested size is zero
117 - You can now profile part of a program's execution using the new
118 `CACHEGRIND_START_INSTRUMENTATION` and `CACHEGRIND_STOP_INSTRUMENTATION`
119 client requests, along with the new `--instr-at-start` option. The
120 behaviour is the same as Callgrind's equivalent functionality.
122 * ==================== FIXED BUGS ====================
124 The following bugs have been fixed or resolved. Note that "n-i-bz"
125 stands for "not in bugzilla" -- that is, a bug that was reported to us
126 but never got a bugzilla entry. We encourage you to file bugs in
127 bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather
128 than mailing the developers (or mailing lists) directly -- bugs that
129 are not entered into bugzilla tend to get forgotten about or ignored.
131 390871 ELF debug info reader confused with multiple .rodata* sections
132 417993 vbit-test fail on s390x with Iop_Add32: spurious dependency on uninit
133 426751 Valgrind reports "still reachable" memory using musl
134 (alpine running inside docker)
135 432801 Valgrind 3.16.1 reports a jump based on uninitialized memory somehow
136 related to clang and signals
137 433857 Add validation to C++17 aligned new/delete alignment size
138 433859 Add mismatched detection to C++ 17 aligned new/delete
139 460192 Add epoll_pwait2
140 461074 DWARF2 CFI reader: unhandled DW_OP_ 0x11 (consts) DW_OP_ 0x92 (bregx)
141 465782 s390x: Valgrind doesn't compile with Clang on s390x
142 466105 aligned_alloc problems, part 2
143 467441 Add mismatched detection to C++ 14 sized delete
144 469049 link failure on ppc64 (big endian) valgrind 3.20
145 469146 massif --ignore-fn does not ignore inlined functions
146 469768 Make it possible to install gdb scripts in a different location
147 470121 Can't run callgrind_control with valgrind 3.21.0 because of perl errors
148 470132 s390x: Assertion failure on VGM instruction
149 470520 Multiple realloc zero errors crash in MC_(eq_Error)
150 470713 Failure on the Yosys project: valgrind: m_libcfile.c:1802
151 (Bool vgPlain_realpath(const HChar *, HChar *)):
152 Assertion 'resolved' failed
153 470830 Don't print actions vgdb me ... continue for vgdb --multi mode
154 470978 s390x: Valgrind cannot start qemu-kvm when "sysctl vm.allocate_pgste=0"
155 471311 gdb --multi mode stdout redirecting to stderr
156 471807 Add support for lazy reading and downloading of DWARF debuginfo
157 472219 Syscall param ppoll(ufds.events) points to uninitialised byte(s)
158 472875 none/tests/s390x/dfp-1 failure
159 472963 Broken regular expression in configure.ac
160 473604 Fix bug472219.c compile failure with Clang 16
161 473677 make check compile failure with Clang 16 based on GCC 13.x
162 473745 must-be-redirected function - strlen
163 473870 FreeBSD 14 applications fail early at startup
164 473944 Handle mold linker split RW PT_LOAD segments correctly
165 474332 aligned_alloc under Valgrind returns nullptr when alignment is not a multiple of sizeof(void *)
166 475650 DRD does not work with C11 threads
167 475652 Missing suppression for __wcsncpy_avx2 (strncpy-avx2.S:308)?
168 476108 vg_replace_malloc DELETE checks size
169 n-i-bz Allow arguments with spaces in .valgrindrc files
170 n-i-bz FreeBSD fixed reading of Valgrind tools own debuginfo
172 To see details of a given bug, visit
173 https://bugs.kde.org/show_bug.cgi?id=XXXXXX
174 where XXXXXX is the bug number as listed above.
176 (3.22.0.RC1: 17 Oct 2023)
177 (3.22.0.RC2: 26 Oct 2023)
179 Release 3.21.0 (28 Apr 2023)
180 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
182 This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux,
183 PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux,
184 MIPS64/Linux, ARM/Android, ARM64/Android, MIPS32/Android, X86/Android,
185 X86/Solaris, AMD64/Solaris, AMD64/MacOSX 10.12, X86/FreeBSD and
186 AMD64/FreeBSD. There is also preliminary support for X86/macOS 10.13,
187 AMD64/macOS 10.13 and nanoMIPS/Linux.
189 * ==================== CORE CHANGES ===================
191 * When GDB is used to debug a program running under valgrind using
192 the valgrind gdbserver, GDB will automatically load some
193 python code provided in valgrind defining GDB front end commands
194 corresponding to the valgrind monitor commands.
195 These GDB front end commands accept the same format as
196 the monitor commands directly sent to the Valgrind gdbserver.
197 These GDB front end commands provide a better integration
198 in the GDB command line interface, so as to use for example
199 GDB auto-completion, command specific help, searching for
200 a command or command help matching a regexp, ...
201 For relevant monitor commands, GDB will evaluate arguments
202 to make the use of monitor commands easier.
203 For example, instead of having to print the address of a variable
204 to pass it to a subsequent monitor command, the GDB front end
205 command will evaluate the address argument. It is for example
207 (gdb) memcheck who_points_at &some_struct sizeof(some_struct)
210 $2 = (some_struct_type *) 0x1130a0 <some_struct>
211 (gdb) p sizeof(some_struct)
213 (gdb) monitor who_point_at 0x1130a0 40
215 * The vgdb utility now supports extended-remote protocol when
216 invoked with --multi. In this mode the GDB run command is
217 supported. Which means you don't need to run gdb and valgrind
218 from different terminals. So for example to start your program
219 in gdb and run it under valgrind you can do:
221 (gdb) set remote exec-file prog
223 (gdb) target extended-remote | vgdb --multi
226 * The behaviour of realloc with a size of zero can now
227 be changed for tools that intercept malloc. Those
228 tools are memcheck, helgrind, drd, massif and dhat.
229 Realloc implementations generally do one of two things
230 - free the memory like free() and return NULL
231 (GNU libc and ptmalloc).
232 - either free the memory and then allocate a
233 minimum sized block or just return the
234 original pointer. Return NULL if the
235 allocation of the minimum sized block fails
236 (jemalloc, musl, snmalloc, Solaris, macOS).
237 When Valgrind is configured and built it will
238 try to match the OS and libc behaviour. However
239 if you are using a non-default library to replace
240 malloc and family (e.g., musl on a glibc Linux or
241 tcmalloc on FreeBSD) then you can use a command line
242 option to change the behaviour of Valgrind:
243 --realloc-zero-bytes-frees=yes|no [yes on Linux glibc, no otherwise]
245 * ================== PLATFORM CHANGES =================
247 * Make the address space limit on FreeBSD amd64 128Gbytes
248 (the same as Linux and Solaris, it was 32Gbytes)
250 * ==================== TOOL CHANGES ===================
253 - When doing a delta leak_search, it is now possible to only
254 output the new loss records compared to the previous leak search.
255 This is available in the memcheck monitor command 'leak_search'
256 by specifying the "new" keyword or in your program by using
257 the client request VALGRIND_DO_NEW_LEAK_CHECK.
258 Whenever a "delta" leak search is done (i.e. when specifying
259 "new" or "increased" or "changed" in the monitor command),
260 the new loss records have a "new" marker.
261 - Valgrind now contains python code that defines GDB memcheck
262 front end monitor commands. See CORE CHANGES.
263 - Performs checks for the use of realloc with a size of zero.
264 This is non-portable and a source of errors. If memcheck
265 detects such a usage it will generate an error
266 realloc() with size 0
267 followed by the usual callstacks.
268 A switch has been added to allow this to be turned off:
269 --show-realloc-size-zero=yes|no [yes]
272 - The option ---history-backtrace-size=<number> allows to configure
273 the number of entries to record in the stack traces of "old"
274 accesses. Previously, this number was hardcoded to 8.
275 - Valgrind now contains python code that defines GDB helgrind
276 front end monitor commands. See CORE CHANGES.
279 - `--cache-sim=no` is now the default. The cache simulation is old and
280 unlikely to match any real modern machine. This means only the `Ir`
281 event are gathered by default, but that is by far the most useful
283 - `cg_annotate`, `cg_diff`, and `cg_merge` have been rewritten in
284 Python. As a result, they all have more flexible command line
285 argument handling, e.g. supporting `--show-percs` and
286 `--no-show-percs` forms as well as the existing `--show-percs=yes`
287 and `--show-percs=no`.
288 - `cg_annotate` has some functional changes.
289 - It's much faster, e.g. 3-4x on common cases.
290 - It now supports diffing (with `--diff`, `--mod-filename`, and
291 `--mod-funcname`) and merging (by passing multiple data files).
292 - It now provides more information at the file and function level.
293 There are now "File:function" and "Function:file" sections. These
294 are very useful for programs that use inlining a lot.
295 - Support for user-annotated files and the `-I`/`--include` option
296 has been removed, because it was of little use and blocked other
298 - The `--auto` option is renamed `--annotate`, though the old
299 `--auto=yes`/`--auto=no` forms are still supported.
300 - `cg_diff` and `cg_merge` are now deprecated, because `cg_annotate`
301 now does a better job of diffing and merging.
302 - The Cachegrind output file format has changed very slightly, but in
303 ways nobody is likely to notice.
306 - Valgrind now contains python code that defines GDB callgrind
307 front end monitor commands. See CORE CHANGES.
310 - Valgrind now contains python code that defines GDB massif
311 front end monitor commands. See CORE CHANGES.
314 - A new kind of user request has been added which allows you to
315 override the 1024 byte limit on access count histograms for blocks
316 of memory. The client request is DHAT_HISTOGRAM_MEMORY.
318 * ==================== FIXED BUGS ====================
320 The following bugs have been fixed or resolved. Note that "n-i-bz"
321 stands for "not in bugzilla" -- that is, a bug that was reported to us
322 but never got a bugzilla entry. We encourage you to file bugs in
323 bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather
324 than mailing the developers (or mailing lists) directly -- bugs that
325 are not entered into bugzilla tend to get forgotten about or ignored.
327 170510 Don't warn about ioctl of size 0 without direction hint
328 241072 List tools in --help output
329 327548 false positive while destroying mutex
330 382034 Testcases build fixes for musl
331 351857 confusing error message about valid command line option
332 374596 inconsistent RDTSCP support on x86_64
333 392331 Spurious lock not held error from inside pthread_cond_timedwait
334 397083 Likely false positive "uninitialised value(s)" for __wmemchr_avx2 and __wmemcmp_avx2_movbe
335 400793 pthread_rwlock_timedwrlock false positive
336 419054 Unhandled syscall getcpu on arm32
337 433873 openat2 syscall unimplemented on Linux
338 434057 Add stdio mode to valgrind's gdbserver
339 435441 valgrind fails to interpose malloc on musl 1.2.2 due to weak symbol name and no libc soname
340 436413 Warn about realloc of size zero
341 439685 compiler warning in callgrind/main.c
342 444110 priv/guest_ppc_toIR.c:36198:31: warning: duplicated 'if' condition.
343 444487 hginfo test detects an extra lock inside data symbol "_rtld_local"
344 444488 Use glibc.pthread.stack_cache_size tunable
345 444568 drd/tests/pth_barrier_thr_cr fails on Fedora 38
346 445743 "The impossible happened: mutex is locked simultaneously by two threads"
347 while using mutexes with priority inheritance and signals
348 449309 Missing loopback device ioctl(s)
349 459476 vgdb: allow address reuse to avoid "address already in use" errorsuse" errors
350 460356 s390: Sqrt32Fx4 -- cannot reduce tree
351 462830 WARNING: unhandled amd64-freebsd syscall: 474
352 463027 broken check for MPX instruction support in assembler
353 464103 Enhancement: add a client request to DHAT to mark memory to be histogrammed
354 464476 Firefox fails to start under Valgrind
355 464609 Valgrind memcheck should support Linux pidfd_open
356 464680 Show issues caused by memory policies like selinux deny_execmem
357 464859 Build failures with GCC-13 (drd tsan_unittest)
358 464969 D language demangling
359 465435 m_libcfile.c:66 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed.
360 466104 aligned_alloc problems, part 1
361 467036 Add time cost statistics for Regtest
362 467482 Build failure on aarch64 Alpine
363 467714 fdleak_* and rlimit tests fail when parent process has more than
364 64 descriptors opened
365 467839 Gdbserver: Improve compatibility of library directory name
366 468401 [PATCH] Add a style file for clang-format
367 468556 Build failure for vgdb
368 468606 build: remove "Valgrind relies on GCC" check/output
369 469097 ppc64(be) doesn't support SCV syscall instruction
370 n-i-bz FreeBSD rfork syscall fail with EINVAL or ENOSYS rather than VG_(unimplemented)
372 To see details of a given bug, visit
373 https://bugs.kde.org/show_bug.cgi?id=XXXXXX
374 where XXXXXX is the bug number as listed above.
376 * ==================== KNOWN ISSUES ===================
378 * configure --enable-lto=yes is know to not work in all setups.
379 See bug 469049. Workaround: Build without LTO.
381 (3.21.0.RC1: 14 Apr 2023)
382 (3.21.0.RC2: 21 Apr 2023)
384 Release 3.20.0 (24 Oct 2022)
385 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
387 This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux,
388 PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux,
389 MIPS64/Linux, ARM/Android, ARM64/Android, MIPS32/Android, X86/Android,
390 X86/Solaris, AMD64/Solaris, AMD64/MacOSX 10.12, X86/FreeBSD and
391 AMD64/FreeBSD. There is also preliminary support for X86/macOS 10.13,
392 AMD64/macOS 10.13 and nanoMIPS/Linux.
394 * ==================== CORE CHANGES ===================
396 * The option "--vgdb-stop-at=event1,event2,..." accepts the new value abexit.
397 This indicates to invoke gdbserver when your program exits abnormally
398 (i.e. with a non zero exit code).
399 * Fix Rust v0 name demangling.
400 * The Linux rseq syscall is now implemented as (silently) returning ENOSYS.
401 * Add FreeBSD syscall wrappers for __specialfd and __realpathat.
402 * Remove FreeBSD dependencies on COMPAT10, which fixes compatibility with
404 * The option --enable-debuginfod=<no|yes> [default: yes] has been added on
406 * More DWARF5 support as generated by clang14.
408 * ==================== FIXED BUGS ====================
410 The following bugs have been fixed or resolved. Note that "n-i-bz"
411 stands for "not in bugzilla" -- that is, a bug that was reported to us
412 but never got a bugzilla entry. We encourage you to file bugs in
413 bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather
414 than mailing the developers (or mailing lists) directly -- bugs that
415 are not entered into bugzilla tend to get forgotten about or ignored.
417 131186 writev reports error in (vector[...])
418 434764 iconv_open causes ld.so v2.28+ to use optimised strncmp
419 446754 Improve error codes from alloc functions under memcheck
420 452274 memcheck crashes with Assertion 'sci->status.what == SsIdle' failed
421 452779 Valgrind fails to build on FreeBSD 13.0 with llvm-devel (15.0.0)
422 453055 shared_timed_mutex drd test fails with "Lock shared failed" message
423 453602 Missing command line option to enable/disable debuginfod
424 452802 Handle lld 9+ split RW PT_LOAD segments correctly
425 454040 s390x: False-positive memcheck:cond in memmem on arch13 systems
426 456171 [PATCH] FreeBSD: Don't record address errors when accessing the 'kern.ps_strings' sysctl struct
427 n-i-bz Implement vgdb invoker on FreeBSD
428 458845 PowerPC: The L field for the dcbf and sync instruction should be
430 458915 Remove register cache to fix 458915 gdbserver causes wrong syscall return
431 459031 Documentation on --error-exitcode incomplete
432 459477 XERROR messages lacks ending '\n' in vgdb
433 462007 Implicit int in none/tests/faultstatus.c
435 To see details of a given bug, visit
436 https://bugs.kde.org/show_bug.cgi?id=XXXXXX
437 where XXXXXX is the bug number as listed above.
439 (3.20.0.RC1: 20 Oct 2022)
442 Release 3.19.0 (11 Apr 2022)
443 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
445 This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux,
446 PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux,
447 MIPS64/Linux, ARM/Android, ARM64/Android, MIPS32/Android, X86/Android,
448 X86/Solaris, AMD64/Solaris, AMD64/MacOSX 10.12, X86/FreeBSD and
449 AMD64/FreeBSD. There is also preliminary support for X86/macOS 10.13,
450 AMD64/macOS 10.13 and nanoMIPS/Linux.
452 * ==================== CORE CHANGES ===================
454 * Fix Rust v0 name demangling.
455 * The Linux rseq syscall is now implemented as (silently) returning ENOSYS.
456 * Add FreeBSD syscall wrappers for __specialfd and __realpathat.
457 * Remove FreeBSD dependencies on COMPAT10, which fixes compatibility with HardenedBSD
459 * ================== PLATFORM CHANGES =================
462 - ignore the "v8.x" architecture levels, only look at actual CPU features
463 present. Fixes mismatch detected between RDMA and atomics features
464 preventing startup on some QEMU configurations.
465 - Implement LD{,A}XP and ST{,L}XP
466 - Fix incorrect code emitted for doubleword CAS.
469 - Fix sys_ipc semtimedop syscall
470 - Fix VFLRX and WFLRX instructions
471 - Fix EXRL instruction with negative offset
474 - Reimplement the vbpermq instruction support to generate less Iops and
475 avoid overflowing internal buffers.
476 - Fix checking for scv support to avoid "Facility 'SCV' unavailable (12),
477 exception" messages in dmsg.
478 - Fix setting condition code for Vector Compare quad word instructions.
479 - Fix fix lxsibzx, lxsihzx and lxsihzx instructions so they only load
480 their respective sized data.
481 - Fix the prefixed stq instruction in PC relative mode.
483 * ==================== TOOL CHANGES ===================
486 - Speed up --track-origins=yes for large (in the range of hundreds to
487 thousands of megabytes) mmap/munmaps.
489 - Several fixes for new versions of libstd++ using new posix try_lock
492 * ==================== FIXED BUGS ====================
494 The following bugs have been fixed or resolved. Note that "n-i-bz"
495 stands for "not in bugzilla" -- that is, a bug that was reported to us
496 but never got a bugzilla entry. We encourage you to file bugs in
497 bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather
498 than mailing the developers (or mailing lists) directly -- bugs that
499 are not entered into bugzilla tend to get forgotten about or ignored.
501 403802 leak_cpp_interior fails with some reachable blocks different than expected
502 435732 memcheck/tests/leak_cpp_interior fails with gcc11
503 444242 s390x: Valgrind crashes on EXRL with negative offset
504 444399 arm64: unhandled instruction 0xC87F2D89 (LD{,A}XP and ST{,L}XP).
506 444481 gdb_server test failures on s390x
507 444495 dhat/tests/copy fails on s390x
508 444552 memcheck/tests/sem fails on s390x with glibc 2.34
509 444571 PPC, fix the lxsibzx and lxsihzx so they only load their respective
511 444836 PPC, pstq instruction for R=1 is not storing to the correct address.
512 444925 fexecve syscall wrapper not properly implemented
513 445032 valgrind/memcheck crash with SIGSEGV when SIGVTALRM timer used and
515 445211 Fix out of tree builds
516 445300 [PATCH] Fix building tests with Musl
517 445011 SIGCHLD is sent when valgrind uses debuginfod-find
518 445354 arm64 backend: incorrect code emitted for doubleword CAS
519 445415 arm64 front end: alignment checks missing for atomic instructions
520 445504 Using C++ condition_variable results in bogus "mutex is locked simultaneously by two threads" warning
521 445607 Unhandled amd64-freebsd syscall: 247
522 445668 Inline stack frame generation is broken for Rust binaries
523 445916 Demangle Rust v0 symbols with .llvm suffix
524 446139 DRD/Helgrind with std::shared_timed_mutex::try_lock_until and try_lock_shared_until false positives
525 446138 DRD/Helgrind with std::timed_mutex::try_lock_until false positives
526 446281 Add a DRD suppression for fwrite
527 446103 Memcheck: `--track-origins=yes` causes extreme slowdowns for large mmap/munmap
528 446139 DRD/Helgrind with std::shared_timed_mutex::try_lock_until and try_lock_shared_until false
529 446251 TARGET_SIGNAL_THR added to enum target_signal
530 446823 FreeBSD - missing syscalls when using libzm4
531 447991 s390x: Valgrind indicates illegal instruction on wflrx
532 447995 Valgrind segfault on power10 due to hwcap checking code
533 449483 Powerpc: vcmpgtsq., vcmpgtuq,, vcmpequq. instructions not setting the
534 condition code correctly.
535 449672 ppc64 --track-origins=yes failures because of bad cmov addHRegUse
536 449838 sigsegv liburing the 'impossible' happened for io_uring_setup
537 450025 Powerc: ACC file not implemented as a logical overlay of the VSR
539 450437 Warn for execve syscall with argv or argv[0] being NULL
540 450536 Powerpc: valgrind throws 'facility scv unavailable exception'
541 451626 Syscall param bpf(attr->raw_tracepoint.name) points to unaddressable byte(s)
542 451827 [ppc64le] VEX temporary storage exhausted with several vbpermq instructions
543 451843 valgrind fails to start on a FreeBSD system which enforces W^X
545 To see details of a given bug, visit
546 https://bugs.kde.org/show_bug.cgi?id=XXXXXX
547 where XXXXXX is the bug number as listed above.
549 (3.19.0.RC1: 02 Apr 2022)
550 (3.19.0.RC2: 08 Apr 2022)