Hi Carl,
On Mon, 2024-04-22 at 11:40 -0700, Carl Love wrote:
> The PowerPC test results for Valgrind 3.23.0.RC1
Thanks. Looks fairly good overall. I haven't studied the rest, but ...
> none/tests/fdleak_ipv4 (stderr) New failure, did not
> fail for valgrind 3.22.0
> none/tests/file_dclose (stderr) New failure, did not
> fail for valgrind 3.22.0
> none/tests/socket_close (stderr) New failure, did not
> fail for valgrind 3.22.0
These are new tests in 3.23.0 and for some reason they "main" part of
the stacktrace is slightly different on different systems. I tried to
work around that with the following commit:
commit 04d30049bf9b4ae14262a50e8a16442e1edf75f8
Author: Mark Wielaard <m...@klomp.org>
Date: Tue Apr 23 14:14:33 2024 +0200
Filter away "main" differences in filter_fdleak
Stack traces showing where fds were created show some differences in
the "main" function, different line numbers, or (in binary) or (below
main). Since the precise location of the original call in the main
function isn't the goal of these tests just filer them all out and
replace them with a simple "main".
Which should be part of RC2 to be published tomorrow.
Cheers,
Mark
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
