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