From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch rfc] Add frame memory & arch methods
Date: Tue, 03 Jun 2003 18:37:00 -0000 [thread overview]
Message-ID: <3EDCEAD9.1060902@redhat.com> (raw)
In-Reply-To: <20030603024137.GA7798@nevyn.them.org>
> On Mon, Jun 02, 2003 at 10:33:29PM -0400, Andrew Cagney wrote:
>
>> >On Mon, Jun 02, 2003 at 08:59:45PM -0400, Andrew Cagney wrote:
>> >
>
>> >>Hello,
>> >>
>> >>This adds per-frame memory and architecture methods. Instead of using
>> >>the global variablecurrent_gdbarch and the context dependant
>> >>read_memory, architecture code can use these. Should help future proof
>> >>architecture code should thread/target changes start happening.
>> >>
>> >>It uses them in the d10v.
>> >>
>> >>I'll commit in a few days.
>
>> >
>> >
>> >Could you explain to us where you see this going? Right now it looks
>> >like a solution without a problem. Sure, someday they may need a
>> >target parameter, but until we're closer to that day I don't see why a
>> >frame parameter is the way to go.
>
>>
>> Ref: [multi-arch] The frame as the global parameter (long, important),
>> http://sources.redhat.com/ml/gdb/2001-02/msg00335.html
>
>
> Very enlightening, thank you!
>
> [To paraphrase you, it sure must be gratifying to see how much of that
> message looks "obvious" now, two years later.]
BTW, some more recent references:
Ref: cooked regcache -> frame
http://sources.redhat.com/ml/gdb/2003-05/msg00287.html
Ref: Deprecate read_memory, write_memory
http://sources.redhat.com/ml/gdb/2003-05/msg00341.html
I've checked this in.
Andrew
prev parent reply other threads:[~2003-06-03 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 1:00 Andrew Cagney
2003-06-03 1:23 ` Daniel Jacobowitz
2003-06-03 2:33 ` Andrew Cagney
2003-06-03 2:41 ` Daniel Jacobowitz
2003-06-03 18:37 ` Andrew Cagney [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=3EDCEAD9.1060902@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
/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