Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
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 18:45:00 -0000	[thread overview]
Message-ID: <3E63A2D5.8010007@redhat.com> (raw)
In-Reply-To: <200303021731.h22HVsEl019548@elgar.kettenis.dyndns.org>

> Folks,
> 
> I've been working on making the i386 target use the new frame
> unwinding stuff.  I'm at a stage where I'm seeing no regressions on
> i386-unknown-freebsd4.7.  So I'd like to check my work in, in the not
> too distant future.  However, this is probably going to cause some
> fallout amongst the other targets.
> 
> As far as I can see *BSD, GNU/Linux, GNU/Hurd, the various System
> V-derived systems (including Solaris 2.x), Netware, DJGPP, Cygwin, and
> the various embedded targets should be fine.
> 
> My changes will break the various Sequent Symmetry targets, and I'll
> probably leave them broken (which they probably already are).
> 
> I'll see whether I can fix LynxOS before actually committing the
> patch.
> 
> However, Interix will need some serious work.  The frame methods it
> redefines will have to be replaced by *_frame_pc_unwind and
> *_frame_id_unwind functions.  Should I leave that to you Joel, or
> would you like me to write some initial versions and leave the
> necessary testing and bug-fixing to you?

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)?

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.

Andrew

(1) The best way of explaining the problem is to document how things work.



  parent reply	other threads:[~2003-03-03 18:45 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 [this message]
2003-03-03 21:32   ` Mark Kettenis
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=3E63A2D5.8010007@redhat.com \
    --to=ac131313@redhat.com \
    --cc=brobecker@act-europe.fr \
    --cc=cfg@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=kettenis@chello.nl \
    --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