Re: [Valgrind-developers] after commit of gdbserver, vgdb.c does not compile on s390x fedora and suse

[Philippe W. <phi...@sk...>]

From: "Maynard Johnson" <may...@us...>
> I also get compile errors with ppc64, but on older distros like SLES 10 and RHEL 5.  The compilation error is different, though:
...
> Valgrind builds OK on SLES 11 SP1.  Comparing ptrace header files between SLES 10 and SLES 11 SP1, I see that PTRACE_{GET|SET}REGS 
> is most assuredly *not* defined in SLES 10.  Is this a PowerPC issue only?

vgdb.c (and the rest of the gdbserver patch) has been compiled on various combinations of arch and platforms.
(a.o. on RHEL5 x86_64).

>From what I can see, depending on the OS and the arch, we can have:
      PTRACE_GETREGS not defined
      PTRACE_GETREGS defined, but returning an error at runtime if used.
      PTRACE_GETREGS defined and working.

I will update vgdb.c so that it handles the above 3 cases (doing checks at compile time
and/or at runtime), which should solve the vgdb.c compilation problem for all linux platforms.

(there is no compilation problem on Darwin, because the ptrace support has not been
done for Darwin. There is however a link problem on Darwin/x86 that I do not understand).


Philippe