From: Pedro Alves <pedro@codesourcery.com>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] nto-procfs.c: Add to_xfer_partial
Date: Mon, 24 Aug 2009 11:34:00 -0000 [thread overview]
Message-ID: <200908241226.59601.pedro@codesourcery.com> (raw)
In-Reply-To: <4A6F5D74.3010108@qnx.com>
On Tuesday 28 July 2009 21:20:04, Aleksandar Ristovski wrote:
> Pedro Alves wrote:
> > On Monday 27 July 2009 20:44:51, Aleksandar Ristovski wrote:
> >> Pedro Alves wrote:
> >>> (( Note: It isn't correct to defer to the target beneath for
> >>> TARGET_OBJECT_MEMORY (and similars) objects, but, I see that nto-procfs.c
> >>> is still implementing deprecated_xfer_memory. ))
> >> Did you want me to make changes here?
> >
> > Nope, consider it an FYI.
> >
> > This offset > 0 check isn't really correct. Would it be hard to
> > make this work with partial transfers?
> >
>
> Implemented.
>
Thanks!
On Tuesday 28 July 2009 21:20:04, Aleksandar Ristovski wrote:
> ndex: gdb/nto-procfs.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/nto-procfs.c,v
> retrieving revision 1.48
> diff -u -p -r1.48 nto-procfs.c
> --- gdb/nto-procfs.c 28 Jul 2009 13:20:26 -0000 1.48
> +++ gdb/nto-procfs.c 28 Jul 2009 20:16:21 -0000
> @@ -872,6 +872,56 @@ procfs_xfer_memory (CORE_ADDR memaddr, g
> return (nbytes);
> }
>
> +static LONGEST
> +procfs_xfer_partial (struct target_ops *ops, enum target_object object,
> + const char *annex, gdb_byte *readbuf,
> + const gdb_byte *writebuf, ULONGEST offset, LONGEST len)
> +{
> + if (object == TARGET_OBJECT_MEMORY)
> + {
> + int nbytes = 0;
> +
> + if (readbuf)
> + return (*ops->deprecated_xfer_memory) (offset, readbuf,
> + len, 0, NULL, ops);
> + else if (writebuf)
> + return (*ops->deprecated_xfer_memory) (offset, (gdb_byte*) writebuf,
> + len, 1, NULL, ops);
> + else
> + return 0;
> + }
Hmmm, copying from procfs.c, are we? If you're going as far as
implementing TARGET_OBJECT_MEMORY, then why stop there and
still defer to ops->deprecated_xfer_memory? You could just ...
> @@ -1405,6 +1455,7 @@ init_procfs_ops (void)
> procfs_ops.to_store_registers = procfs_store_registers;
> procfs_ops.to_prepare_to_store = procfs_prepare_to_store;
> procfs_ops.deprecated_xfer_memory = procfs_xfer_memory;
... not install this ^^^^ and have procfs_xfer_partial call
procfs_xfer_memory directly (might as well adjust its
arguments/interface on the way).
> + procfs_ops.to_xfer_partial = procfs_xfer_partial;
Anyway, the patch looks fine to me as is. Feel free to go
ahead and check it in.
--
Pedro Alves
prev parent reply other threads:[~2009-08-24 11:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 20:31 Aleksandar Ristovski
2009-06-11 21:36 ` Pierre Muller
2009-06-12 2:25 ` Aleksandar Ristovski
2009-06-12 6:55 ` Pierre Muller
2009-06-18 15:16 ` Aleksandar Ristovski
2009-07-07 16:23 ` Aleksandar Ristovski
2009-07-21 15:45 ` Aleksandar Ristovski
2009-07-24 14:16 ` Pedro Alves
2009-07-27 20:17 ` Aleksandar Ristovski
2009-07-28 12:01 ` Pedro Alves
2009-07-28 22:17 ` Aleksandar Ristovski
2009-08-24 11:34 ` Pedro Alves [this message]
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=200908241226.59601.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=aristovski@qnx.com \
--cc=gdb-patches@sourceware.org \
/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