Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: gdb-patches@sourceware.cygnus.com
Cc: "J.T. Conklin" <jtc@redback.com>
Subject: [PATCH]: go32_xfer_memory and memory attributes
Date: Sat, 03 Feb 2001 23:46:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1010204093640.20547O-100000@is> (raw)

FYI: this change:

   2001-01-23  J.T. Conklin  <jtc@redback.com>

          * target.h (#include "memattr.h"): Added.
          (target_ops.to_xfer_memory): Add attrib argument.

broke the DJGPP port, because the function which implements the 
to_xfer_memory method was not updated.

I fixed that today with the following patch:

2001-02-04  Eli Zaretskii  <eliz@is.elta.co.il>

	* go32-nat.c (go32_xfer_memory): Make the argument list consistent
	with target.h's to_xfer_memory member.

--- gdb/go32-nat.c~0	Sun Aug  6 10:19:38 2000
+++ gdb/go32-nat.c	Sat Feb  3 15:22:20 2001
@@ -157,7 +157,9 @@
 static void go32_store_registers (int regno);
 static void go32_prepare_to_store (void);
 static int go32_xfer_memory (CORE_ADDR memaddr, char *myaddr, int len,
-			     int write, struct target_ops *target);
+			     int write,
+			     struct mem_attrib *attrib,
+			     struct target_ops *target);
 static void go32_files_info (struct target_ops *target);
 static void go32_stop (void);
 static void go32_kill_inferior (void);
@@ -539,6 +541,7 @@
 
 static int
 go32_xfer_memory (CORE_ADDR memaddr, char *myaddr, int len, int write,
+		  struct mem_attrib *attrib ATTRIBUTE_UNUSED,
 		  struct target_ops *target ATTRIBUTE_UNUSED)
 {
   if (write)


                 reply	other threads:[~2001-02-03 23:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.SUN.3.91.1010204093640.20547O-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=jtc@redback.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