From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com, rearnsha@arm.com
Subject: Re: [RFA/ARM] Framificate the ARM port [2/3]
Date: Tue, 01 Jul 2003 13:59:00 -0000 [thread overview]
Message-ID: <20030701135913.GA10520@nevyn.them.org> (raw)
In-Reply-To: <3F018A64.4010801@redhat.com>
On Tue, Jul 01, 2003 at 09:19:32AM -0400, Andrew Cagney wrote:
> >The second of three patches. The last of the boring ones.
> >
> >This patch changes ARM to build an entire cache before setting any
> >information in the frame. It includes some nasty hacks (for instance,
> >at one point it calls deprecated_get_next_frame_hack to get the sentinel
> >frame); don't worry, I swear they'll all go away in patch #3.
>
> So it's useful! Looking at the first patch, and arm_get_cache, perhaphs
> there should also be a:
>
> void **deprecated_get_this_frame_cache (next_frame);
>
> method.
Yeah, this would probably have been useful.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-07-01 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 22:52 Daniel Jacobowitz
2003-07-01 13:19 ` Andrew Cagney
2003-07-01 13:59 ` Daniel Jacobowitz [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=20030701135913.GA10520@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=rearnsha@arm.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