From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Randolph Chung <randolph@tausq.org>,
Jim Blandy <jimb@red-bean.com>,
gdb-patches@sources.redhat.com
Subject: Re: [hppa] FYI: confusion in unwind descriptor field meaning
Date: Sun, 13 Nov 2005 18:45:00 -0000 [thread overview]
Message-ID: <20051113182851.GD3599@nevyn.them.org> (raw)
In-Reply-To: <20051113182255.GV1635@adacore.com>
On Sun, Nov 13, 2005 at 10:22:55AM -0800, Joel Brobecker wrote:
> > If you're going to do this, I recommend using the prologue analysis
> > framework Jim posted, which hopefully we'll have merged by then. If we
> > haven't, well, an active user of it will make it easier.
>
> There was some discussion about redesigning it a bit at the time.
> I think it was something to make the analyser use callbacks in
> the tdep code, as opposed to us calling the appropriate routines
> in the analyzer. Is this still in the air (or maybe I am just
> confused)?
Maybe? :-)
I tend to review things backwards in time; it's going to be a while
before I can work my way back to Jim's post again. I need to play
around with it before I'll have an opinion.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-11-13 18:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 23:55 Joel Brobecker
2005-11-10 1:27 ` Randolph Chung
2005-11-10 1:31 ` Joel Brobecker
2005-11-10 1:32 ` Randolph Chung
2005-11-10 19:18 ` Randolph Chung
2005-11-11 11:22 ` Joel Brobecker
2005-11-12 3:32 ` Randolph Chung
2005-11-12 4:22 ` Jim Blandy
2005-11-12 4:39 ` Jim Blandy
2005-11-12 4:59 ` Randolph Chung
2005-11-12 5:07 ` Jim Blandy
2005-11-12 13:21 ` Randolph Chung
2005-11-12 17:08 ` Jim Blandy
2005-11-13 15:38 ` Randolph Chung
2005-11-13 18:27 ` Daniel Jacobowitz
2005-11-19 19:15 ` Randolph Chung
2005-11-13 18:23 ` Joel Brobecker
2005-11-13 18:28 ` Daniel Jacobowitz
2005-11-13 18:36 ` Joel Brobecker
2005-11-13 18:45 ` 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=20051113182851.GD3599@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@red-bean.com \
--cc=randolph@tausq.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