This is the mail archive of the
mailing list for the GDB project.
Re: New ARI warning Wed Jun 23 01:54:57 UTC 2010
- From: "Ulrich Weigand" <uweigand at de dot ibm dot com>
- To: dan at codesourcery dot com (Daniel Jacobowitz)
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 24 Jun 2010 17:14:52 +0200 (CEST)
- Subject: Re: New ARI warning Wed Jun 23 01:54:57 UTC 2010
> 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
The ARI claims "read_memory" and "write_memory" as "to be deprecated"
interfaces. These were added by Andrew Cagney 2003-05-24:
at about the time he introduced get_frame_memory:
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 ...
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE