Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 7 May 2020 22:13:53 +0200
From:      Paul Floyd <pjfloyd@wanadoo.fr>
To:        FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject:   Re: Call for testers - Valgrind
Message-ID:  <02D4832B-4BEB-440D-879F-DB625E4CE946@wanadoo.fr>
In-Reply-To: <CAPyFy2Aryy0uDuTQDyUAmM0iUOo_XVXCJXpfxXBcrar6XhB=QQ@mail.gmail.com>
References:  <453259393.837.1588660255688.JavaMail.www@wwinf1m04> <CAPyFy2Aryy0uDuTQDyUAmM0iUOo_XVXCJXpfxXBcrar6XhB=QQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Ed


> On 7 May 2020, at 20:10, Ed Maste <emaste@freebsd.org> wrote:
>=20
> On Tue, 5 May 2020 at 02:31, Paul FLOYD <pjfloyd@wanadoo.fr> wrote:
>>=20
>> Hi
>>=20
>> I've done a lot of work since the start of the year trying to reboot =
Valgrind on FreeBSD. Whilst there is still a way to go, the results are =
looking promising.
>=20
> Thank you very much for picking this up!
>=20
>> I'd like to get some feedback, in particular from developers that use =
debug versions of Qt and libc and who are capable of telling whether any =
errors produced are false positives or not.
>=20
> I'll try to take a look at libc.
>=20
>> Supported Platforms
>> ~~~~~~~~~~~~~
>> I've set up VirtualBox VMs as far back as FreeBSD 10 and tested that =
at least everything builds. I've been doing fairly extensive testing =
(with Valgrind's own regression suite) on 12.1 amd64
>> and i386. I'll set up a 13.0-CURRENT VM soon to ensure that I'm ready =
for the next release.
>=20
> How are Valgrind's test results looking?


There are around 710 tests for amd64 and around 650 tests for i386. When =
everything is compiled with GCC then I get a bit less than 20 failures =
on amd64. The figure goes up to about 60 failures for i386 and building =
everything with clang. I=E2=80=99m still working through the i386 and =
clang related issues.

I=E2=80=99m tracking issues on GitHub as they are analysed.


>=20
>> 4. There are still numerous missing syscalls.
>=20
> Do we have a list of the missing ones?
>=20


There=E2=80=99s a fairly large number of syscalls that predate FreeBSD =
10 and are not implemented. Here are the ones added in FreeBSD 10 or =
later that aren=E2=80=99t implemented.

    // futimens                                 546
    // utimensat                                547
    /* 548 is obsolete numa_getaffinity */
    /* 549 is obsolete numa_setaffinity */
    // fdatasync                                550
    // fstatat                                  552
    // fhstat                                   553
    // getdirentries                            554
    // mknodat                                  559
    // kevent                                   560
    // cpuset_getdomain                         561
    // cpuset_setdomain                         562
    // getfhat                                  564
    // fhlink                                   565
    // fhlinkat                                 566
    // fhreadlink                               567

A+
Paul=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?02D4832B-4BEB-440D-879F-DB625E4CE946>