From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: dan@codesourcery.com (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org
Subject: Re: New ARI warning Wed Jun 23 01:54:57 UTC 2010
Date: Thu, 24 Jun 2010 15:15:00 -0000 [thread overview]
Message-ID: <201006241514.o5OFEqvt021907@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20100624145616.GA31306@caradoc.them.org> from "Daniel Jacobowitz" at Jun 24, 2010 10:56:19 AM
Dan Jacobowitz:
> On Wed, Jun 23, 2010 at 01:54:57AM +0000, GDB Administrator wrote:
> > 493a494,495
> > > gdb/i386-tdep.c:543: deprecate: read_memory: Replace read_memory() with regcache_read() et.al.
> > gdb/i386-tdep.c:543: read_memory (from, buf, len);
> > > gdb/i386-tdep.c:557: deprecate: write_memory: Replace write_memory() with regcache_read() et.al.
> > gdb/i386-tdep.c:557: write_memory (to, buf, len);
>
> Am I missing something here? Why would you replace read_memory with
> regcache_read?
The ARI claims "read_memory" and "write_memory" as "to be deprecated"
interfaces. These were added by Andrew Cagney 2003-05-24:
http://sources.redhat.com/ml/gdb/2003-05/msg00341.html
at about the time he introduced get_frame_memory:
http://sourceware.org/ml/gdb-patches/2003-06/msg00104.html
The idea seems to have been that all memory access was supposed to
identify the process/thread/target where the memory resided by
means of passing a frame.
However, this was never really fully pursues, it seems. I'm not
really sure it still makes sense to keep these ARI entries ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2010-06-24 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 1:55 GDB Administrator
2010-06-24 14:56 ` Daniel Jacobowitz
2010-06-24 15:14 ` Pierre Muller
2010-06-24 15:15 ` Daniel Jacobowitz
2010-06-24 17:58 ` Michael Snyder
2010-06-24 15:15 ` Ulrich Weigand [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=201006241514.o5OFEqvt021907@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=dan@codesourcery.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