Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Pedro Alves'" <pedro@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: [OBV] fix procfs.c compilation failure
Date: Mon, 25 May 2009 12:30:00 -0000	[thread overview]
Message-ID: <008301c9dd34$65036910$2f0a3b30$@u-strasbg.fr> (raw)

Pedro,

you apparently missed procfs_wait from procfs.c source
when you added the options parameter.

  This patch allows to compile successfully on i386 OpenSolaris
again.

  Checked in as obvious.

  I have no idea if options value should be handled
inside procfs_wait... as I didn't really try to understand
why you added that parameter.
  Could you check if you think that the code should be modified to handle
non-zero options arg?

Pierre Muller
Pascal language support maintainer for GDB



ChangeLog entry:
2009-05-25  Pierre Muller  <muller@ics.u-strasbg.fr>

       * procfs.c (procfs_wait): Add options parameter.

Index: procfs.c
===================================================================
RCS file: /cvs/src/src/gdb/procfs.c,v
retrieving revision 1.108
diff -u -p -r1.108 procfs.c
--- procfs.c    18 May 2009 00:58:38 -0000      1.108
+++ procfs.c    25 May 2009 12:23:35 -0000
@@ -128,7 +128,7 @@ static void procfs_mourn_inferior (struc
 static void procfs_create_inferior (struct target_ops *, char *,
                                    char *, char **, int);
 static ptid_t procfs_wait (struct target_ops *,
-                          ptid_t, struct target_waitstatus *);
+                          ptid_t, struct target_waitstatus *, int);
 static int procfs_xfer_memory (CORE_ADDR, gdb_byte *, int, int,
                               struct mem_attrib *attrib,
                               struct target_ops *);
@@ -3947,7 +3947,7 @@ syscall_is_lwp_create (procinfo *pi, int

 static ptid_t
 procfs_wait (struct target_ops *ops,
-            ptid_t ptid, struct target_waitstatus *status)
+            ptid_t ptid, struct target_waitstatus *status, int options)
 {
   /* First cut: loosely based on original version 2.1 */
   procinfo *pi;


             reply	other threads:[~2009-05-25 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25 12:30 Pierre Muller [this message]
2009-05-25 12:43 ` Pedro Alves

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='008301c9dd34$65036910$2f0a3b30$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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