Re: Valgrind on arm64

Paul,

This is what I'm getting:

== 701 tests, 4 stderr failures, 0 stdout failures, 0 stderrB failures,
0 stdoutB failures, 9 post failures ==
memcheck/tests/descr_belowsp             (stderr)
memcheck/tests/manuel1                   (stderr)
memcheck/tests/supp_unknown              (stderr)
none/tests/socket_close                  (stderr)

I've got less tests executed though. I'll try to find something else to
test, but this box is usually used for the DPAA2 drivers development,
i.e. nothing specific is installed there.

If anyone has an idea, I'd be glad to try :)

Regards,
Dmitry

Paul Floyd <paulf2718@gmail.com> writes:

> On 14-03-24 09:27, Dmitry Salychev wrote:
>> Hi,
>> I've built and installed it on my Honeycomb LX2:
>> FreeBSD armforge 14.0-RELEASE-p5 FreeBSD 14.0-RELEASE-p5 #0
>> releng/14.0-n265410-adfda3c395fa: Thu Mar 14 08:03:01 CET 2024
>> root@armforge:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC
>> arm64 aarch64 1400097 1400097
>> Are there quick tests to run?
>> Regards,
>> Dmitry
>
> Hi Dmitry
>
> Thanks for trying it out.
>
> There are Valgrind's own regression tests.
>
> gmake check
> gmake regtest
>
> I get
>
> == 725 tests, 5 stderr failures, 0 stdout failures, 0 stderrB
> failures, 0 stdoutB failures, 0 post failures ==
> memcheck/tests/descr_belowsp             (stderr)
> memcheck/tests/manuel1                   (stderr)
> memcheck/tests/supp_unknown              (stderr)
> memcheck/tests/thread_alloca             (stderr)
> none/tests/socket_close                  (stderr)
>
> I'm not sure about thread_alloca, the others aren't serious.
>
> After that, just try anything that your system can cope with.
>
> A+
> Paul


-- 
https://wiki.freebsd.org/DmitrySalychev