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

[Florian K. <fl...@ei...>]

Hi Mark,

On 09.10.25 22:03, Mark Wielaard wrote:
> 
> 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.

Oh yes! Can't wait :)

> Please let me know what you believe are blockers for the release or
> fixes you really would like to see in.
> 

I looked at building valgrind on mips (cfarm230 machine) because there are no 
nightly runs..
If mips is a supported platform (?), then there is a bit of work there:

configury:
Need to detect presence of -lcrypto and -laio otherwise
memcheck/tests/linux/bug480706.c
memcheck/tests/linux/bug420682_1.c
memcheck/tests/linux/bug420682_2.c
will not build.

The GCC on that machine is rather old: 8.3.0. It does not recognise
-Wno-missing-exception-spec
-Wno-implicit-exception-spec-mismatch
-Wno-alloc-size-larger-than
-Walloc-size-larger-than=

Building:
There are 126 warnings about:
   cast increases required alignment of target type
I do not know whether that is a problem (other than performance degradation) or 
not. If it is not then those warnings should be suppressed. Back in the days we 
were striving to have a clean build/check/regtest which I personally find to be 
a laudable goal.

Regtest:

== 768 tests, 288 stderr failures, 60 stdout failures, 10 stderrB failures, 11 
stdoutB failures, 3 post failures ==

Essentially all memcheck tests are failing this way:

valgrind:  Fatal error at startup: a function redirection
valgrind:  which is mandatory for this platform-tool combination
valgrind:  cannot be set up.  Details of the redirection are:
....

which renders memcheck unusable. libc6-dbg appears to be installed, though.
I guess a MAINTAINERS file would be good to find out whom to pester with this :)

For PPC there is https://bugs.kde.org/show_bug.cgi?id=508661 which would be good 
to get fixed.

Cheers,
    Florian