From: rbrown64@csc.com.au
To: gdb-patches@sources.redhat.com
Cc: Michael Snyder <msnyder@redhat.com>
Subject: Unixware gdb/procfs.c patch - v3
Date: Thu, 17 Jan 2002 17:14:00 -0000 [thread overview]
Message-ID: <OFB2B67E40.BE12B87A-ONCA256B45.00064544@int.csc.com.au> (raw)
procfs.c hides the particular type of process status structure in
the gdb_prstatus_t typedef. Push this information hiding into
bfd/elf.c(elfcore_write_gdb_prstatus) exporting one interface.
No regressions on UnixWare 7.1.0 and Solaris 2.7 with this and the
matching bfd/elf.c patch.
2001-01-18 Rodney Brown <rbrown64@csc.com.au>
* procfs.c: Prototype elfcore_write_gdb_prstatus,
elfcore_write_prfpreg, elfcore_write_prpsinfo.
(procfs_do_thread_registers): Call elfcore_write_gdb_prstatus.
--- procfs.c.orig Tue Jan 15 15:01:48 2002
--- procfs.c.orig Tue Jan 15 15:01:48 2002
+++ procfs.c Thu Jan 17 16:59:00 2002
@@ -55,7 +55,7 @@ Inc., 59 Temple Place - Suite 330, Bosto
* Unixware
* AIX5
*
- * /proc works by immitating a file system: you open a simulated file
+ * /proc works by imitating a file system: you open a simulated file
* that represents the process you wish to interact with, and
* perform operations on that "file" in order to examine or change
* the state of the other process.
@@ -325,6 +325,10 @@ typedef prstatus_t gdb_prstatus_t;
typedef prstatus_t gdb_lwpstatus_t;
#endif /* NEW_PROC_API */
+char *elfcore_write_gdb_prstatus (bfd *, char *, int *, long, int, void *);
+char *elfcore_write_prfpreg (bfd *, char *, int *, void *, int);
+char *elfcore_write_prpsinfo (bfd *, char *, int *, char *, char *);
+
typedef struct procinfo {
struct procinfo *next;
int pid; /* Process ID */
@@ -5733,12 +5737,12 @@ procfs_do_thread_registers (bfd *obfd, p
merged_pid = TIDGET (ptid) << 16 | PIDGET (ptid);
fill_gregset (&gregs, -1);
- note_data = (char *) elfcore_write_prstatus (obfd,
- note_data,
- note_size,
- merged_pid,
- stop_signal,
- &gregs);
+ note_data = (char *) elfcore_write_gdb_prstatus (obfd,
+ note_data,
+ note_size,
+ merged_pid,
+ stop_signal,
+ &gregs);
fill_fpregset (&fpregs, -1);
note_data = (char *) elfcore_write_prfpreg (obfd,
note_data,
next reply other threads:[~2002-01-18 1:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 17:14 rbrown64 [this message]
2002-01-17 17:48 ` 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=OFB2B67E40.BE12B87A-ONCA256B45.00064544@int.csc.com.au \
--to=rbrown64@csc.com.au \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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