On 16/09/14 00:00, Patrick J. LoPresti wrote: > PTRACE_GETSIGINFO definitely exists on SLES10 SP3 64-bit: > > suse10$ cat /etc/issue > > Welcome to SUSE Linux Enterprise Server 10 SP3 (x86_64) - Kernel \r (\l). > > suse10$ find /usr/include -type f | xargs grep PTRACE_GETSIGINFO > /usr/include/linux/ptrace.h:#define PTRACE_GETSIGINFO 0x4202 > suse10$ rpm -qf /usr/include/linux/ptrace.h > glibc-devel-2.4-31.77.76.1 > > > This is on a testing system I have lying around... No time to try > compiling Valgrind there at the moment, though. > > Does Valgrind #include <linux/ptrace.h> ? A quick scan of the headers > on SLES10 suggests <sys/ptrace.h> is not sufficient to pick up this > #define...
As a general rule nothing in userspace should be including things from the linux directory - those are the kernel interfaces not the C library interfaces so would only be appropriate if you were going to invoke the system call directly. Yes, most of the time it doesn't make any difference because the C library will just pass flags through to the system call, but it's really up to the C library to know that and to arrange to pass the definitions through. So I think the original diagnosis stands, that the C library is too old to know about this flag. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
