From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Correct semantics of target_read_partial, add target_read_whole
Date: Wed, 05 Jul 2006 19:34:00 -0000 [thread overview]
Message-ID: <200607051934.k65JYHQk000845@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060705190639.GA26278@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 5 Jul 2006 15:06:39 -0400)
> Date: Wed, 5 Jul 2006 15:06:39 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> Here is an improved version of my previous patch. According to
> suggestions I received, I've renamed target_read_whole to the hopefully
> clearer target_read_object_alloc (since it reads an entire object, and
> allocates memory for it).
Hmm, target_read also reads objects (although not necessary complete
objects), but doesn't have "object" in its name. Perhaps I have an
unhealthy sense for symmetry, but I'd rather have the new function
named target_read_alloc. It's shorter too ;-).
Otherwise, this really lloks good!
> 2006-07-05 Daniel Jacobowitz <dan@codesourcery.com>
>
> * target.c (target_read): Stop if target_read_partial returns 0
> when some bytes have already been read.
> (target_write): Likewise for target_write_partial.
> (target_read_partial, target_write_partial): Make static.
> (target_read_object_alloc): New.
> * target.h: Doc fixes.
> (target_read_partial, target_write_partial): Delete prototypes.
> (target_read_object_alloc): New prototype.
>
> * auxv.c (target_auxv_read): Delete.
> (target_auxv_search, fprint_target_auxv): Use target_read_object_alloc.
> * auxv.h (target_auxv_read): Delete prototype.
> * avr-tdep.c (avr_io_reg_read_command): Use target_read_object_alloc.
> * ia64-tdep.c (getunwind_table, get_kernel_table): Likewise.
> * linux-nat.c (linux_nat_make_corefile_notes): Likewise.
> * procfs.c (procfs_make_note_section): Likewise.
> * remote.c (remote_xfer_partial): Don't loop here.
> * sparc-tdep.c (sparc_fetch_wcookie): Use target_read.
next prev parent reply other threads:[~2006-07-05 19:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 3:24 Daniel Jacobowitz
2006-06-22 18:25 ` Mark Kettenis
2006-06-22 18:37 ` Daniel Jacobowitz
2006-06-29 9:35 ` Vladimir Prus
2006-06-24 10:06 ` Vladimir Prus
2006-06-26 13:38 ` Daniel Jacobowitz
2006-06-28 8:18 ` Vladimir Prus
2006-06-28 13:49 ` Daniel Jacobowitz
2006-07-05 19:06 ` Daniel Jacobowitz
2006-07-05 19:34 ` Mark Kettenis [this message]
2006-07-12 18:15 ` 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=200607051934.k65JYHQk000845@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--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