Re: Valgrind-3.26.0.RC1 is available for testing
Abhay Kandpal via Valgrind-developers <valgrind-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org> Thu, 23 Oct 2025 16:10:23 +0530
| Newsgroups | gmane.comp.debugging.valgrind.devel,gmane.comp.debugging.valgrind |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============8978574316255268064==
Content-Type: multipart/alternative;
boundary="------------7jMwhNw9d0ELr4w1KiyxVNjb"
Content-Language: en-GB
This is a multi-part message in MIME format.
--------------7jMwhNw9d0ELr4w1KiyxVNjb
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi Mark,
I tested on ppcle 10 with GCC 14.3.1 and GLIBC 2.40
Below are new failures observed.
== 794 tests, 6 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/mcleak (stderr)
gdbserver_tests/mcleak (stderrB)
memcheck/tests/leak-delta (stderr)
memcheck/tests/linux/rfcomm (stderr)
helgrind/tests/getaddrinfo (stderr)
none/tests/fdleak_cmsg_xml (stderr)
none/tests/socket_close_xml (stderr)
Comparing with older release below are new two
none/tests/fdleak_cmsg_xml (stderr)
none/tests/socket_close_xml (stderr)
The above two failure are regular and non-critical in nature. Hence they are not blocker for this release.
I tested on other power versions also and found similar result.
We will investigate the new regression after the release.
Regards
Abhay Kandpal
On 18/10/25 08:13, Mark Wielaard wrote:
> An RC1 tarball for 3.26.0 is now available at
> https://sourceware.org/pub/valgrind/valgrind-3.26.0.RC1.tar.bz2
> (md5sum = b7798804b18476104073009043ecc96d)
> (sha1sum = bc1bffd272b3a14b3ba9c1cc5a25a5e3975b9c8a)
> https://sourceware.org/pub/valgrind/valgrind-3.26.0.RC1.tar.bz2.asc
>
> Please give it a try in configurations that are important for you and
> report any problems you have, either on this mailing list, or
> (preferably) via our bug tracker at
> https://bugs.kde.org/enter_bug.cgi?product=valgrind
>
> The final 3.26.0 release is scheduled for Fri Oct 24.
>
>
> _______________________________________________
> Valgrind-developers mailing list
> Valgrind-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers
--------------7jMwhNw9d0ELr4w1KiyxVNjb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<pre>
Hi Mark,
I tested on ppcle 10 with GCC 14.3.1 and GLIBC 2.40
Below are new failures observed.
== 794 tests, 6 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/mcleak (stderr)
gdbserver_tests/mcleak (stderrB)
memcheck/tests/leak-delta (stderr)
memcheck/tests/linux/rfcomm (stderr)
helgrind/tests/getaddrinfo (stderr)
none/tests/fdleak_cmsg_xml (stderr)
none/tests/socket_close_xml (stderr)
Comparing with older release below are new two
none/tests/fdleak_cmsg_xml (stderr)
none/tests/socket_close_xml (stderr)
The above two failure are regular and non-critical in nature. Hence they are not blocker for this release.
I tested on other power versions also and found similar result.
We will investigate the new regression after the release.
Regards
Abhay Kandpal
</pre>
<div class="moz-cite-prefix">On 18/10/25 08:13, Mark Wielaard wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20251018024359.GE16295-ccHWXNLP7XmvZOhXRs0CNB2eb7JE58TQ@public.gmane.org">
<pre wrap="" class="moz-quote-pre">An RC1 tarball for 3.26.0 is now available at
<a class="moz-txt-link-freetext" href="https://sourceware.org/pub/valgrind/valgrind-3.26.0.RC1.tar.bz2">https://sourceware.org/pub/valgrind/valgrind-3.26.0.RC1.tar.bz2</a>
(md5sum = b7798804b18476104073009043ecc96d)
(sha1sum = bc1bffd272b3a14b3ba9c1cc5a25a5e3975b9c8a)
<a class="moz-txt-link-freetext" href="https://sourceware.org/pub/valgrind/valgrind-3.26.0.RC1.tar.bz2.asc">https://sourceware.org/pub/valgrind/valgrind-3.26.0.RC1.tar.bz2.asc</a>
Please give it a try in configurations that are important for you and
report any problems you have, either on this mailing list, or
(preferably) via our bug tracker at
<a class="moz-txt-link-freetext" href="https://bugs.kde.org/enter_bug.cgi?product=valgrind">https://bugs.kde.org/enter_bug.cgi?product=valgrind</a>
The final 3.26.0 release is scheduled for Fri Oct 24.
_______________________________________________
Valgrind-developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Valgrind-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org">Valgrind-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/valgrind-developers">https://lists.sourceforge.net/lists/listinfo/valgrind-developers</a>
</pre>
</blockquote>
</body>
</html>
--------------7jMwhNw9d0ELr4w1KiyxVNjb--
--===============8978574316255268064==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--===============8978574316255268064==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Valgrind-developers mailing list
Valgrind-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
--===============8978574316255268064==--