Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: gdb@sources.redhat.com
Subject: ptrace(2) autoconf tests
Date: Sun, 08 Aug 2004 21:00:00 -0000	[thread overview]
Message-ID: <200408082100.i78L0BdZ005809@elgar.kettenis.dyndns.org> (raw)

FYI,

I'm working on ptrace(2) autoconf tests.  I think I've got a real
nifty way to find the correct one.  It'd be great though if people
could post the ptrace prototypes from the headers on their systems.
You can find them in <sys/ptrace.h>, <unistd.h> or <ptrace.h>.  Thus
far I've got:

Ancient UNIX		int ptrace (int, int, int *, int);
BSD			int ptrace (int, pid_t, caddr_t, int);
GNU/Linux		long int ptrace (enum __request, ...);
HP-UX 11.00 (32-bit)	int ptrace (int, pid_t, int, int, int);
HP-UX 11.00 (64-bit)	long ptrace (int, pid_t, long, long, long);
Solaris 2.9		long ptrace (int, pid_t, long, long);

and

AIX 5.2L		int ptrace (int, int, int *, int, int *);
Tru64 5.1A		int ptrace (long, long int, ulong_t *, ulong_t);

The latter two are snatched from the manual pages.  I'd like to verify
them against the header files.

Cheers,

Mark


             reply	other threads:[~2004-08-08 21:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-08 21:00 Mark Kettenis [this message]
2004-08-08 21:42 ` Michael Chastain
2004-08-09  0:46   ` Mark Kettenis
2004-08-09  7:19     ` Michael Chastain
2004-08-09 13:09     ` Andrew Cagney
2004-08-09 15:34       ` Mark Kettenis
2004-08-09 15:53         ` Andrew Cagney
2004-08-09  5:37 ` Joel Brobecker
2004-08-09 21:52   ` Mark Kettenis
2004-08-10  5:49     ` Joel Brobecker
2004-08-10  6:56       ` Michael Chastain
2004-08-10  7:20         ` Marcel Moolenaar
2004-08-10 14:45           ` John David Anglin
2004-08-10 18:52             ` Joel Brobecker
2004-08-11  2:16               ` John David Anglin
2004-08-10 19:03     ` Joel Brobecker
     [not found] <no.id>
2004-08-11  2:55 ` John David Anglin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200408082100.i78L0BdZ005809@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox