Valgrind on arm64

[Paul Floyd]

Hi

[reposting the same message that I posted to the Userland forum]

I'm close to being ready with a port of Valgrind on arm64 (currently
only i386 and amd64 are officially supported).

I'd appreciate it if anyone could build and test it.

The git repo is here
https://github.com/paulfloyd/freebsdarm64_valgrind

To build, run the following
autogen.sh
configure --prefix=where_you_want_to_install
gmake
gmake install

Iif you have GCC installed run configure with "CC=clang CXX=clang++".
If you prefer not to install it, you can run it from the build directory
with the script "vg-in-place".

There's one more issue that I'd like to iron out - DRD isn't detecting
pthread_barrier issues. After that I'll push the code upstream and
update the devel/valgrind-devel port.

I expect Valgrind 3.23 will be out by the end of April and I'll update
devel/valgrind at that time.


A+
Paul


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Dmitry Salychev]

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
***@armforge:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC
arm64 aarch64 1400097 1400097

Are there quick tests to run?

Regards,
Dmitry

Post by Paul Floyd
Hi
[reposting the same message that I posted to the Userland forum]
I'm close to being ready with a port of Valgrind on arm64 (currently
only i386 and amd64 are officially supported).
I'd appreciate it if anyone could build and test it.
The git repo is here
https://github.com/paulfloyd/freebsdarm64_valgrind
To build, run the following
autogen.sh
configure --prefix=where_you_want_to_install
gmake
gmake install
Iif you have GCC installed run configure with "CC=clang CXX=clang++".
If you prefer not to install it, you can run it from the build
directory with the script "vg-in-place".
There's one more issue that I'd like to iron out - DRD isn't detecting
pthread_barrier issues. After that I'll push the code upstream and
update the devel/valgrind-devel port.
I expect Valgrind 3.23 will be out by the end of April and I'll update
devel/valgrind at that time.
A+
Paul

[Paul Floyd]

Post by Dmitry Salychev
Hi,
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
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



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Paul Floyd]

Post by Dmitry Salychev
Paul,
== 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.

Hi Dmitry

There are tests that depend on various things like CPU features detected
and whether the mqueuefs + sctp modules have been loaded. The biggest
dependency is on gdb - 23 of them.

Otherwise that looks a lot like what I get on my RPi 5.

A+
Paul



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Dmitry Salychev]

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

Post by Paul Floyd

Post by Dmitry Salychev
Hi,
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
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