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