Date: Thu, 7 May 2020 14:10:17 -0400 From: Ed Maste <emaste@freebsd.org> To: Paul FLOYD <pjfloyd@wanadoo.fr> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Call for testers - Valgrind Message-ID: <CAPyFy2Aryy0uDuTQDyUAmM0iUOo_XVXCJXpfxXBcrar6XhB=QQ@mail.gmail.com> In-Reply-To: <453259393.837.1588660255688.JavaMail.www@wwinf1m04> References: <453259393.837.1588660255688.JavaMail.www@wwinf1m04>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 5 May 2020 at 02:31, Paul FLOYD <pjfloyd@wanadoo.fr> wrote: > > Hi > > 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. Thank you very much for picking this up! > 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. I'll try to take a look at libc. > 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. How are Valgrind's test results looking? > 4. There are still numerous missing syscalls. Do we have a list of the missing ones?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2Aryy0uDuTQDyUAmM0iUOo_XVXCJXpfxXBcrar6XhB=QQ>