This is the mail archive of the
mailing list for the GDB project.
Re: Seems like a bug in target_read_stack / dcache_xfer_memory?
- From: "drow at false dot org" <drow at false dot org>
- To: Michael Snyder <msnyder at vmware dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Sun, 18 Oct 2009 18:51:34 -0400
- Subject: Re: Seems like a bug in target_read_stack / dcache_xfer_memory?
- References: <4ADB9759.email@example.com>
On Sun, Oct 18, 2009 at 03:31:53PM -0700, Michael Snyder wrote:
> The arguments and return
> value are just as for target_xfer_partial
The comment is on the logical home of this method, other places should
refer to the header: the definition of to_xfer_partial in struct
target_ops in target.h.
> Anyway, I don't even remember now how I figured this out, but
> I *THINK* what all these guys return is either 0 for success,
> or an errno value less than zoro.
No, they return:
the number of bytes actually transfered, zero when no
further transfer is possible, and -1 when the transfer is not