From: "Maciej W. Rozycki" <macro@mips.com>
To: gdb-patches@sourceware.org
Cc: Nigel Stephens <nigel@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: remote-mips.c: Update the prototype of mips_xfer_memory()
Date: Thu, 22 Mar 2007 13:20:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0703221256160.19009@perivale.mips.com> (raw)
Hello,
The deprecated_xfer_memory() member of "struct target_ops" takes
"gdb_byte *" as the second argument now. This change updates
remote-mips.c accordingly.
This change should be obvious, though it cannot be tested with the tree
as is, as for whatever reason the file is currently not built in any
configuration. I tested it successfully with the "mipsisa32-sde-elf"
target with a patch that enables this file to be built, which I will
submit later on.
2007-03-22 Nigel Stephens <nigel@mips.com>
Maciej W. Rozycki <macro@mips.com>
* remote-mips.c (mips_xfer_memory): Update prototype.
OK to apply?
Maciej
12036.diff
Index: gdb/src/gdb/remote-mips.c
===================================================================
--- gdb.orig/src/gdb/remote-mips.c 2007-02-13 13:51:16.000000000 +0000
+++ gdb/src/gdb/remote-mips.c 2007-02-13 13:51:23.000000000 +0000
@@ -108,7 +108,7 @@
static int mips_store_word (CORE_ADDR addr, unsigned int value,
char *old_contents);
-static int mips_xfer_memory (CORE_ADDR memaddr, char *myaddr, int len,
+static int mips_xfer_memory (CORE_ADDR memaddr, gdb_byte *myaddr, int len,
int write,
struct mem_attrib *attrib,
struct target_ops *target);
@@ -2029,7 +2029,7 @@
static int mask_address_p = 1;
static int
-mips_xfer_memory (CORE_ADDR memaddr, char *myaddr, int len, int write,
+mips_xfer_memory (CORE_ADDR memaddr, gdb_byte *myaddr, int len, int write,
struct mem_attrib *attrib, struct target_ops *target)
{
int i;
next reply other threads:[~2007-03-22 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 13:20 Maciej W. Rozycki [this message]
2007-03-22 13:41 ` Daniel Jacobowitz
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.LNX.4.61.0703221256160.19009@perivale.mips.com \
--to=macro@mips.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=nigel@mips.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