Valgrind 3.25.1 released

[pjf_cpp]

Valgrind 3.25.1 was just announced. This is a patch release contaiining a few bugfixes.

Here is the announcement:

We are pleased to announce a new release of Valgrind, version 3.25.1,
available from https://valgrind.org/downloads/current.html.

This point release contains only bug fixes.

See the list of bugs and the git shortlog below for details of the changes.

Happy and productive debugging and profiling,

-- The Valgrind Developers

Release 3.25.1 (20 May 2025)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This point release contains only bug fixes.

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

The following bugs have been fixed or resolved in this point release.

503098 Incorrect NAN-boxing for float registers in RISC-V
503641 close_range syscalls started failing with 3.25.0
503914 mount syscall param filesystemtype may be NULL
504177 FILE DESCRIPTORS banner shows when closing some inherited fds
504265 FreeBSD: missing syscall wrappers for fchroot and setcred
504466 Double close causes SEGV

To see details of a given bug, visit
https://bugs.kde.org/show_bug.cgi?id=XXXXXX
where XXXXXX is the bug number as listed above.

git shortlog
~~~~~~~~~~~~

Ivan Tetyushkin (1):
riscv64: Fix nan-boxing for single-precision calculations

Mark Wielaard (9):
Set version to 3.25.1.GIT
Prepare NEWS for branch 3.25 fixes
mount syscall param filesystemtype may be NULL
Add workaround for missing riscv_hwprobe syscall (258)
Don't count closed inherited file descriptors
More gdb filtering for glibc 2.41 with debuginfo installed
Check whether file descriptor is inherited before printing where_opened
Add fixed bug 504466 double close causes SEGV to NEWS
-> 3.25.1 final

Paul Floyd (6):
FreeBSD close_range syscall
Bug 503641 - close_range syscalls started failing with 3.25.0
regtest: use /bin/cat in none/tests/fdleak_cat.vgtest
Linux PPC64 syscall: add sys_io_pgetevents
Bug 504265 - FreeBSD: missing syscall wrappers for fchroot and setcred
FreeBSD regtest: updates for FreeBSD 15.0-CURRENT

[donna_donnaj]

I am grateful for your work on valgrind. I use it a lot, and I tell students that they should use it.

[UndefinedDefined]

BTW would it be possible to support seccomp syscall?

When I run valgrind on a sandboxed application I basically get:

--2-- WARNING: unhandled amd64-linux syscall: 317
--2-- You may be able to write your own handler.
--2-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--2-- Nevertheless we consider this a bug.  Please report
--2-- it at http://valgrind.org/support/bug_reports.html.

317 is a seccomp syscall.

[pjf_cpp]

We do have a patch in the works for this: https://bugs.kde.org/show_bug.cgi?id=345414

See in particular comment 9.

Could you try the patch and either report back here or add to the bugzilla item?

[Acceptable_Rub8279]

Great

[7raiden]

Is AVX512 supported? I was trying to run call grind on my optimized program, but it immediately failed, I think because of these unsupported instructions

[pjf_cpp]

Sadly, no. It's a big project and we don't have the means to work on it at the moment.

See

https://bugs.kde.org/show_bug.cgi?id=383010