From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Daniel Jacobowitz'" <dan@codesourcery.com>,
<gdb-patches@sourceware.org>
Subject: RE: New ARI warning Wed Jun 23 01:54:57 UTC 2010
Date: Thu, 24 Jun 2010 15:14:00 -0000 [thread overview]
Message-ID: <002501cb13af$e723d1c0$b56b7540$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20100624145616.GA31306@caradoc.them.org>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Daniel Jacobowitz
> Envoyé : Thursday, June 24, 2010 4:56 PM
> À : gdb-patches@sourceware.org
> Objet : 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);
I don't really know the origin of this rule,
but if you look up the sources, you will see that 'read_memory'
is defined in gdbcore.h
So this function should be specific for core management, no?
Maybe it would be better to suggest using target_read_memory
function in this rule.
Pierre
next prev parent reply other threads:[~2010-06-24 15:14 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 [this message]
2010-06-24 15:15 ` Daniel Jacobowitz
2010-06-24 17:58 ` Michael Snyder
2010-06-24 15:15 ` Ulrich Weigand
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='002501cb13af$e723d1c0$b56b7540$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--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