From: Mark Kettenis <kettenis@chello.nl>
To: ac131313@redhat.com
Cc: gdb@sources.redhat.com, cfg@redhat.com,
thropej@wasavisystems.com, rjl@sco.com,
peter.schauer@regent.e-technik.tu-muenchen.de,
brobecker@act-europe.fr
Subject: Re: HEADS UP: converting the i386 to the new frame unwinding stuff
Date: Mon, 03 Mar 2003 21:32:00 -0000 [thread overview]
Message-ID: <200303032130.h23LUm3g002018@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3E63A2D5.8010007@redhat.com> (message from Andrew Cagney on Mon, 03 Mar 2003 13:45:41 -0500)
Date: Mon, 03 Mar 2003 13:45:41 -0500
From: Andrew Cagney <ac131313@redhat.com>
Mark,
Per several recent discussions, can you create a branch and commit it to
that. That way I can look at it now (regardless of your intended commit
schedule)?
Brilliant idea. I still have to comment my code a bit better, but
I'll try to create that branch somehwere at the end of the week.
I've started writing up the doco and in doing it, I suspect I may have
found an `off by one' error with the unwinder cache. Having a second
implementation using the current code should help sort this out.
The current state of affairs seems to work quite well for the i386.
The only thing that puzzles me is that apparently my
i386_frame_register_unwind gets called without an initialized cache.
I was under the impression that we'd always unwind the pc first, and
since my i386_frame_pc_unwind initialized the cache, I'd always have
an initialized cache with the other unwind functions.
Mark
next prev parent reply other threads:[~2003-03-03 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 17:52 Mark Kettenis
2003-03-02 17:43 ` Joel Brobecker
2003-03-03 14:09 ` Michal Ludvig
2003-03-03 18:45 ` Andrew Cagney
2003-03-03 21:32 ` Mark Kettenis [this message]
2003-03-04 14:28 ` Andrew Cagney
2003-03-05 5:15 ` Andrew Cagney
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=200303032130.h23LUm3g002018@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=ac131313@redhat.com \
--cc=brobecker@act-europe.fr \
--cc=cfg@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=peter.schauer@regent.e-technik.tu-muenchen.de \
--cc=rjl@sco.com \
--cc=thropej@wasavisystems.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).