From: Michael Chastain <mec.gnu@mindspring.com>
To: kettenis@chello.nl, gdb@sources.redhat.com
Subject: Re: ptrace(2) autoconf tests
Date: Sun, 08 Aug 2004 21:42:00 -0000 [thread overview]
Message-ID: <41169E38.nail4UJ11C6PT@mindspring.com> (raw)
In-Reply-To: <200408082100.i78L0BdZ005809@elgar.kettenis.dyndns.org>
Here's all the ptrace(2) prototypes I found on hp testdrive machines.
Michael C
===
alpha-unknown-freebsd5.1
/usr/include/sys/ptrace.h
int ptrace(int _request, pid_t _pid, caddr_t _addr, int _data);
man 2 ptrace
int ptrace(int request, pid_t pid, caddr_t addr, int data);
alphaev56-dec-osf4.0g
/usr/include
no prototype found anywhere
man 2 ptrace
int ptrace ( long request, long int process, ulong_t *address, ulong_t data );
alphaev68-dec-osf5.1b
/usr/include
no prototype found anywhere
man 2 ptrace
int ptrace ( long int request, long int process, ulong_t *address, ulong_t data );
alphaev67-unknown-linux-gnu + debian-unknown
alphaev67-unknown-linux-gnu + redhat-7.2
i686-pc-linux-gnu + debian-unknown
ia64-unknown-linux-gnu + debian-woody
/usr/include/sys/ptrace.h
extern long int ptrace (enum __ptrace_request __request, ...) __THROW;
man 2 ptrace
long int ptrace(enum __ptrace_request request, pid_t pid, void * addr, void * data);
i686-pc-linux-gnu + mandrake 10.0
i686-pc-linux-gnu + redhat-3AS
i686-pc-linux-gnu + redhat-3ES
i686-pc-linux-gnu + suse-9
ia64-unknown-linux-gnu + redhat-3AS
ia64-unknown-linux-gnu + suse-9
/usr/include/sys/ptrace.h
extern long int ptrace (enum __ptrace_request __request, ...) __THROW;
man 2 ptrace
long ptrace(enum __ptrace_request request, pid_t pid, void *addr, void *data);
hppa2.0w-hp-hpux11.11
/usr/include/sys/ptrace.h
#if !defined(__STDC_32__MODE__)
extern long ptrace(int, pid_t, long, long, long);
extern int64_t ptrace64(int, pid_t, uint64_t, uint64_t, uint64_t);
#else
extern int ptrace(int, pid_t, int, int, int);
#endif
man 2 ptrace
int ptrace( int request, pid_t pid, int addr, int data, int addr2);
ia64-hp-hpux11.23
/usr/include/sys/ptrace.h
#if !defined(__STDC_32__MODE__)
# if defined(__ia64) && !defined(_LIBC)
/* pragmas needed to support -B protected */
# pragma extern ptrace64
# endif
extern long ptrace(int, pid_t, long, long, long);
extern int64_t ptrace64(int, pid_t, uint64_t, uint64_t, uint64_t);
#else
extern int ptrace(int, pid_t, int, int, int);
#endif
man 2 ptrace
long ptrace( int request, pid_t pid, long addr, long data, long addr2);
i386-unknown-freebsd4.9
i386-unknown-netbsdelf1.6
/usr/include/sys/ptrace.h
int ptrace __P((int _request, pid_t _pid, caddr_t _addr, int _data));
man 2 ptrace
int ptrace(int request, pid_t pid, caddr_t addr, int data);
next prev parent reply other threads:[~2004-08-08 21:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-08 21:00 Mark Kettenis
2004-08-08 21:42 ` Michael Chastain [this message]
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=41169E38.nail4UJ11C6PT@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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