From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: gdb-patches@sourceware.org
Subject: Re: [rfa] frame address size incorrect if address size != ptr size
Date: Thu, 05 Aug 2010 14:59:00 -0000 [thread overview]
Message-ID: <201008051458.o75EwqoA018388@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20100805143039.GF4610@calimero.vinschen.de> from "Corinna Vinschen" at Aug 05, 2010 04:30:39 PM
Corinna Vinschen wrote:
> I'm going to create a patch which defines and uses a new
> gdbarch_dwarf2_addr_size function. It will be defined as a variable
> like this in gdbarch.sh:
>
> v:int:dwarf2_addr_size:::sizeof (void*):0:gdbarch_ptr_bit (gdbarch) / TARGET_CHAR_BIT:
Looks good, thanks.
> Given that, and also given that I will remove the redundant setting of
> cie->addr_size in decode_frame_entry_1, I have one question left.
>
> What about that comment in decode_frame_entry_1?
>
> If we only use either the V4 addr_size, or the gdbarch_dwarf2_addr_size
> function, then the comment really doesn't make much sense anymore in that
> spot. I'm wondering if it should be moved to the gdbarch.sh file. What
> do you think?
I agree. In fact, the comment in gdbarch.sh could even be expanded to
say that gdbarch_dwarf2_addr_size needs to be defined if and only if the
platform GCC back-end defines a non-default DWARF2_ADDR_SIZE (and is only
necessary if Dwarf versions < 4 need to be supported).
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2010-08-05 14:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 14:53 Corinna Vinschen
2010-08-04 11:35 ` Corinna Vinschen
2010-08-04 22:40 ` Jan Kratochvil
2010-08-05 8:06 ` Corinna Vinschen
2010-08-05 10:04 ` Ulrich Weigand
2010-08-05 12:30 ` Corinna Vinschen
2010-08-05 14:08 ` Ulrich Weigand
2010-08-05 14:30 ` Corinna Vinschen
2010-08-05 14:59 ` Ulrich Weigand [this message]
2010-08-05 15:30 ` Corinna Vinschen
2010-08-05 16:52 ` Ulrich Weigand
2010-08-06 10:48 ` Corinna Vinschen
2010-08-06 11:17 ` Mark Kettenis
2010-08-06 12:01 ` Corinna Vinschen
2010-08-06 14:51 ` Ulrich Weigand
2010-08-06 15:57 ` Corinna Vinschen
2010-08-06 16:27 ` Ulrich Weigand
2010-08-06 16:59 ` Corinna Vinschen
2010-08-06 19:03 ` Corinna Vinschen
2010-08-08 14:55 ` Ulrich Weigand
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=201008051458.o75EwqoA018388@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
/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).