Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: ac131313@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [i386newframe/PATCH] New i386newframe branch
Date: Fri, 02 May 2003 09:29:00 -0000	[thread overview]
Message-ID: <200305020929.h429TS9O030634@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3EB18FDE.9020106@redhat.com> (message from Andrew Cagney on Thu, 01 May 2003 17:21:34 -0400)

   Date: Thu, 01 May 2003 17:21:34 -0400
   From: Andrew Cagney <ac131313@redhat.com>

   >    > +  return &i386_frame_unwind;
   >    > +}
   > 
   >    Have you tried adding just the sigtramp unwinder?  I should get just 
   >    that addition debugged regardless - it should make migrating other ISAs 
   >    easier.
   > 
   > No I haven't.  I don't think I can.  The problem is that I simplified
   > the sigtramp unwinder a bit.  However in order to do so, I need to be
   > able to trust the normal unwinder to unwind the stack pointer
   > correctly.  Unfortunately the current code is a bit sloppy about this.

   Ah, yes, I know the feeling.  Tighten the camshaft cover, and a 
   push-rods slips.  Put that back, and the ....  Some times it's easier to 
   just replace the engine.

   It is unfortunatly something of an all or nothing afair.  I might still 
   get curious though to see just what happens.

I might have something else for you to toy with.  I've a prototype of
a DWARF2 CFI unwinder ready, which is working fine in my i386newframe
branch.  I still need to clean up several hacks, but I might be able
to check it in soon.

Mark


  reply	other threads:[~2003-05-02  9:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-19 16:51 Mark Kettenis
2003-04-29  1:50 ` Andrew Cagney
2003-05-01 20:54   ` Mark Kettenis
2003-05-01 21:21     ` Andrew Cagney
2003-05-02  9:29       ` Mark Kettenis [this message]
2003-05-03 19:36         ` Andrew Cagney
2003-05-03 20:53           ` Mark Kettenis
2003-05-03 22:27             ` Daniel Jacobowitz
2003-05-04  0:28               ` 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=200305020929.h429TS9O030634@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=ac131313@redhat.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