From: Michael Snyder <msnyder@cygnus.com>
To: binutils@sources.redhat.com, nickc@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: [RFA] Change "pid_t" param to long (portability)
Date: Thu, 10 Jan 2002 11:40:00 -0000 [thread overview]
Message-ID: <200201101935.g0AJZSt06600@reddwarf.cygnus.com> (raw)
Not surprisingly, the "pid_t" parameter declaration does not
compile on some systems.
2002-01-10 Michael Snyder <msnyder@redhat.com>
* elf.c (elfcore_write_prstatus): Use long instead of pid_t;
(elfcore_write_pstatus): Use long instead of pid_t;
* elf-bfd.h: Change prototypes to use long instead of pid_t;
Index: elf.c
===================================================================
RCS file: /cvs/src/src/bfd/elf.c,v
retrieving revision 1.120
diff -c -3 -p -r1.120 elf.c
*** elf.c 2002/01/09 18:59:11 1.120
--- elf.c 2002/01/10 19:38:36
*************** elfcore_write_prstatus (abfd, buf, bufsi
*** 6562,6568 ****
bfd *abfd;
char *buf;
int *bufsiz;
! pid_t pid;
int cursig;
void *gregs;
{
--- 6562,6568 ----
bfd *abfd;
char *buf;
int *bufsiz;
! long pid;
int cursig;
void *gregs;
{
*************** elfcore_write_pstatus (abfd, buf, bufsiz
*** 6584,6590 ****
bfd *abfd;
char *buf;
int *bufsiz;
! pid_t pid;
int cursig;
void *gregs;
{
--- 6584,6590 ----
bfd *abfd;
char *buf;
int *bufsiz;
! long pid;
int cursig;
void *gregs;
{
Index: elf-bfd.h
===================================================================
RCS file: /cvs/src/src/bfd/elf-bfd.h,v
retrieving revision 1.63
diff -c -3 -p -r1.63 elf-bfd.h
*** elf-bfd.h 2002/01/08 21:31:36 1.63
--- elf-bfd.h 2002/01/10 19:38:36
*************** extern char *elfcore_write_note
*** 1524,1532 ****
extern char *elfcore_write_prpsinfo
PARAMS ((bfd *, char *, int *, char *, char *));
extern char *elfcore_write_prstatus
! PARAMS ((bfd *, char *, int *, pid_t, int, void *));
extern char * elfcore_write_pstatus
! PARAMS ((bfd *, char *, int *, pid_t, int, void *));
extern char *elfcore_write_prfpreg
PARAMS ((bfd *, char *, int *, void *, int));
extern char *elfcore_write_prxfpreg
--- 1524,1532 ----
extern char *elfcore_write_prpsinfo
PARAMS ((bfd *, char *, int *, char *, char *));
extern char *elfcore_write_prstatus
! PARAMS ((bfd *, char *, int *, long, int, void *));
extern char * elfcore_write_pstatus
! PARAMS ((bfd *, char *, int *, long, int, void *));
extern char *elfcore_write_prfpreg
PARAMS ((bfd *, char *, int *, void *, int));
extern char *elfcore_write_prxfpreg
next reply other threads:[~2002-01-10 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 11:40 Michael Snyder [this message]
2002-01-10 13:16 ` Richard Henderson
2002-01-10 15:06 ` Michael Snyder
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=200201101935.g0AJZSt06600@reddwarf.cygnus.com \
--to=msnyder@cygnus.com \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickc@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