Re: [Valgrind-developers] [valgrind] Suppress FSGSBASE flag from cpuid results

[Paul F. <pj...@wa...>]

> On 14 Mar 2019, at 19:16, Ed Maste <em...@fr...> wrote:
> 
> On Thu, 14 Mar 2019 at 11:20, Tom Hughes <tom...@so...> wrote:
>> 
>> commit 09566120e705d8831aaa7076b439d3ad90b78773
>> Author: Tom Hughes <to...@co...>
>> Date:   Thu Mar 14 15:15:41 2019 +0000
>> 
>>    Suppress FSGSBASE flag from cpuid results
>> 
>>    We don't support {rd,wr}{fs,gs}base so we shouldn't say we do.
> 
> Thanks, I have rebased the FreeBSD patch set on master now and the
> test results are consistent with earlier runs.
> 


Hi

Since I have a bit of free time on my hands (one more week in theory), I’ve also been looking at the FreeBSD port of Valgrind.

Has any work been done on this since last March?

I now have FreeBSD 12.1 reinstalled with Phil Longstaff’s work plus a few of my changes. It seems to work at least for trivial tests - I haven’t yet tried running the regression tests.

At the moment there are 4 things that I see that I need to do

1. Rebase everything onto the main Valgrind development branch
2. I’ve noticed that there is a big issue with clang compiled executables. The problem is that the binaries have 3 PT_LOAD sections (ro, rx, rw) while GCC (and clang on Linux) only generates 2 (rw and rx). This is causing symtab loading to fail. This limits the usefulness somewhat.
3. There were a lot of syscall changes in FreeBSD 12, so I think that ‘configure’ needs to handle/define a freebsd_version variable.
4. There are still quite a few missing syscalls.

A+
Paul