From: Andreas Jaeger <aj@suse.de>
To: Michal Ludvig <mludvig@suse.cz>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH/i386newframe] amd64newframe
Date: Mon, 19 May 2003 07:09:00 -0000 [thread overview]
Message-ID: <u865o74dle.fsf@gromit.moeb> (raw)
In-Reply-To: <3EC8810F.3040905@suse.cz> (Michal Ludvig's message of "Mon, 19 May 2003 09:00:31 +0200")
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).
>
> Anyway thanks for moving amd64 target to the new unwinder!
Yes, thanks! Michal, can you help testing, please?
> BTW could we add amd64 as an alias to x86_64 for configure scripts?
config.* handles it already correctly,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2003-05-19 7:09 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 [this message]
2003-05-19 17:15 ` Mark Kettenis
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=u865o74dle.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
--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