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