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