debug.ptrace_attach_transparent=0

See also

https://bugs.freebsd.org/bugzilla/show\_bug.cgi?id=290008

* ==================== TOOL CHANGES ===================

* There is a new utility script, "vgstack". It has two option, -h for minimal help, and -v for the version information. In normal use pass it the PID of a running Valgrind process and it will perform a vgdb attach and print the backtrace(s) of the guest executable.

* Memcheck handling of aligned allocation functions with a size of zero has changed.

Firstly, 'free_aligned_sized' with a size of zero is no longer considered an error. This was intended so that deallocation had the same behaviour as allocation. In practice, platforms that allow aligned allocation with a size of zero will already generate an error at allocation. Other platforms will get an 'Invalid free' error. The case where the allocation and deallocation sizes are different with the deallocation size being zero is already covered by "Mismatched [alloc/dealloc\] size" errors.

Secondly, the three C aligned allocation functions memalign, aligned_alloc and posix_memalign have a different error message if used with a size of zero. Previously the error was "[function\] invalid size value: [number\]". This was an overstatement of the issue. The problem is that such usage is not portable across platforms. memalign and aligned_alloc are poorly documented, saying things like "Behavior is undefined if size is not an integral multiple of alignment.". Clearly this does not include negative integers though it does not say so explicitly. Does that include zero? posix_memalign is well documented but says that using a size of 0 is implementation-defined. These functions now produce an error "Unsafe allocation with size of zero is implementation-defined". The associated suppression name has also changed from "BadSize" to "UnsafeZeroSize".

Checks for C23 free_sized and free_aligned_sized have been added to Linux. Almost no libraries support these functions yet, with the exception being Google tcmalloc.

* ==================== FIXED BUGS ====================

The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter\_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored.

286849 [PATCH\] Interceptors for new/delete on Darwin were erroneously

commented out in r12043

306098 s390x: Alternate opcode form for convert to/from fixed and friends

309100 s390x: Testcases for extended BFP

309554 Wrap syscall remap_file_pages (216)

331311 Valgrind shows open files in /proc/self/fd that don't work for the process

338803 Handling of dwz debug alt files or cross-CU is broken

368791 Handle swapon and swapoff syscalls as linux generic

369030 Wrap linux syscall: 171 (setdomainname)

388526 Inconsistent severity in message text: "WARNING: Serious error"

418756 MAP_FIXED_NOREPLACE mmap flag unsupported

454276 Some IPC syscalls is missing for x86 linux

476465 AArch64 ARMv8.3 LDAPR/LDAPRH/LDAPRB instructions not supported

493430 Review all syscalls that use or return (new) file descriptors

493434 Add --track-fds=bad mode (no "leak" tracking)

501741 syscall cachestat not wrapped

502359 Add --modify-fds=yes option

502968 Wrap linux specific syscalls 457 (listmount) and 458 (statmount)

503098 Incorrect NAN-boxing for float registers in RISC-V

503241 s390x: Support z17 changes to the NNPA instruction

503641 close_range syscalls started failing with 3.25.0

503677 duplicated-cond compiler warning in dis_RV64M

503817 s390x: fix 'ordered comparison of pointer with integer zero' compiler warnings

503914 mount syscall param filesystemtype may be NULL

503969 Make test results of make ltpchecks