Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: aj@suse.de
Cc: mludvig@suse.cz, gdb-patches@sources.redhat.com
Subject: Re: [PATCH/i386newframe] amd64newframe
Date: Mon, 19 May 2003 17:15:00 -0000	[thread overview]
Message-ID: <200305191715.h4JHFCei001220@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <u865o74dle.fsf@gromit.moeb> (message from Andreas Jaeger on Mon, 19 May 2003 09:09:33 +0200)

   Cc: Mark Kettenis <kettenis@chello.nl>, gdb-patches@sources.redhat.com
   From: Andreas Jaeger <aj@suse.de>
   Date: Mon, 19 May 2003 09:09:33 +0200
   User-Agent: Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.4 (Portable Code, linux)
   Content-Type: text/plain; charset=us-ascii

   Michal Ludvig <mludvig@suse.cz> writes:

   > Mark Kettenis told me that:
   >>    (gdb)    warning: Unmapped DWARF Register #16 encountered
   >>    6       return 0;
   >>    (gdb)    warning: Unmapped DWARF Register #16 encountered
   >>    7       }
   >> Ah, that must be the new DWARF CFI frame unwinder.  The return
   >> address
   >> RA isn't mapped.  I could change the DWARF register mapping in
   >> x86-64-tdep.c, but this really is a problem with the DWARF CFI frame
   >> unwinder since the compiler is free to choose any number it wants for
   >> the return address column.  Should be fixed now.
   >
   > IMHO compiler shouldn't choose whatever it wants - RA column is
   > defined in the Amd64 ABI (sec.3.6).

Ah, but the DWARF specification allows the compiler to choose the
number of the RA column.  Even if the amd64 ABI says the RA is in
column 16, there might be other platforms where the column number
changes from frame to frame.  The current code is more correct than
the old code regardless of what we choose to do on amd64.

   > Anyway thanks for moving amd64 target to the new unwinder!

   Yes, thanks!  Michal, can you help testing, please?

Yes, that would be great.  As soon as it performs better than the old
stuff, I'd like to move things over to mainline.

Mark


  reply	other threads:[~2003-05-19 17:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17 18:34 Andreas Jaeger
2003-05-17 22:26 ` Mark Kettenis
2003-05-19  7:00   ` Michal Ludvig
2003-05-19  7:09     ` Andreas Jaeger
2003-05-19 17:15       ` Mark Kettenis [this message]
2003-05-19 19:54         ` Elena Zannoni
2003-05-19 22:31           ` Elena Zannoni
2003-05-20  5:49         ` Michal Ludvig
  -- strict thread matches above, loose matches on Subject: below --
2003-05-17 15:19 Mark Kettenis
2003-05-19 15:31 ` Elena Zannoni
2003-05-19 17:11   ` Mark Kettenis
2003-05-19 21:24     ` Michal Ludvig
2003-05-19 21:40       ` Daniel Jacobowitz
2003-05-19 22:24       ` Elena Zannoni

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=200305191715.h4JHFCei001220@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=aj@suse.de \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mludvig@suse.cz \
    /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