From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: New ARI warning Wed Sep 29 01:54:08 UTC 2010
Date: Wed, 29 Sep 2010 22:25:00 -0000 [thread overview]
Message-ID: <201009291800.28269.pedro@codesourcery.com> (raw)
In-Reply-To: <20100929163246.GN3007@adacore.com>
On Wednesday 29 September 2010 17:32:47, Joel Brobecker wrote:
> > 1096a1097,1099
> > > gdb/ravenscar-sparc-thread.c:71: deprecate: read_memory: Replace read_memory() with regcache_read() et.al.
> > gdb/ravenscar-sparc-thread.c:71: read_memory (register_addr, buf, buf_size);
> > > gdb/ravenscar-sparc-thread.c:173: deprecate: write_memory: Replace write_memory() with regcache_read() et.al.
> > gdb/ravenscar-sparc-thread.c:173: write_memory (register_address,
> > > gdb/ravenscar-thread.c:156: deprecate: read_memory: Replace read_memory() with regcache_read() et.al.
> > gdb/ravenscar-thread.c:156: read_memory (object_addr, buf, buf_size);
>
> I can fix the warnings, but are we really planning on removing
> read/write_memory (and why?). I can use target_read_memory instead,
> but I don't get the suggestion about regcache_read...
The ARI suggestion makes no sense. It's the ARI that needs fixing.
My guess is that the intention was to suggest replacing
read_register() with regcache_read() at.al. (that is, s/memory/register)
read_register/write_register have been yanked out from the sources
already few years ago.
--
Pedro Alves
next prev parent reply other threads:[~2010-09-29 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 13:34 GDB Administrator
2010-09-29 18:55 ` Joel Brobecker
2010-09-29 22:25 ` Pedro Alves [this message]
2010-09-30 1:36 ` Joel Brobecker
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=201009291800.28269.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).