Re: [Valgrind-developers] Preparing for Valgrind 3.26.0 (RC on Oct 17, final Oct 24)

[Paul F. <pj...@wa...>]

On 2025-10-09 22:03, Mark Wielaard wrote:
> Hi Valgrind hackers,
>
> Normally we do a major releases in April and October. We did do a minor
> 3.25.1 release in May. And the VALGRIND_3_25_BRANCH does contain a
> couple more backported fixes. But the main branch has 350+ more commits
> so it is time to prepare for a new major release.
>
> I am proposing to do a release on Friday October 24. With an RC1 a
> week before, Friday October 17. And possibly an RC2 in between if we
> find some big issue for which we like more testing.
>
> There are a couple of things I like to add before RC1:
>
> - Update to GPLv3+.
>    We discussed this on the list and then with some core developers
>    asking for advice from the FSF Legal and Compliance team.
>    I'll post a patch tomorrow with the full rational, so we can
>    discuss it before applying for RC1.
>
> - Don't warn about fcntl F_GETFD with --track-fds
>    https://bugs.kde.org/show_bug.cgi?id=510436
>    --track-fds=bad is great, but Paul correctly pointed out
>    that there has to be a way for an application to explicitly
>    check for bad fds that doesn't generate an error.
>
> - Removing glibc extra syscall frames might crash
>    https://bugs.kde.org/show_bug.cgi?id=507188
>    This seems to only happen on i386 debian, but it a generic issue
>    with syscall frame filtering.
>
>    And if I have time I also like to finish the removal of artificial
>    frames from the backtraces. There is already support for tracking
>    these artificial frams since commit f7dccaab11b8 "Rewrite DWARF
>    inlined subroutine handling to work cross CU". But they aren't yet
>    filtered.
>
> - On Fedora 43 (beta) for amd64 we get some make regtest failures
>    I haven't really investigated yet, but on f42 we get zero failures,
>    so it would be nice to see what updates caused the new failures.
>
> Please let me know what you believe are blockers for the release or
> fixes you really would like to see in.


Hi Mark


Just two for me

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

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

Also

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

would be nice (and have fairly large impact) but I don't think that I'll 
have enough time.


A+

Paul