From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Rouslan Korneychuk <rouslank@msn.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: DW_AT_count is the same as DW_AT_upper_bound?
Date: Fri, 05 Jul 2013 19:08:00 -0000 [thread overview]
Message-ID: <20130705190844.GA1296@host2.jankratochvil.net> (raw)
In-Reply-To: <BAY171-W1225181D47297CD8C224728D67D0@phx.gbl>
On Fri, 05 Jul 2013 20:41:02 +0200, Rouslan Korneychuk wrote:
> I'm using DW_AT_count instead of DW_AT_upper_bound so that "stack" can
> be empty (have 0 elements), but these two attributes appear to be
> treated the same. Is this a bug or am I misunderstanding something? I'm
> using GDB version 7.5.1.
DW_AT_upper_bound vs. DW_AT_count is described in DWARF-4:
The DW_AT_upper_bound attribute may be replaced by a DW_AT_count
attribute, whose value describes the number of elements in the
subrange rather than the value of the last element.
But your sample DWARF is a case of dynamic bounds which are supported only in
experimental branch(es) so far:
http://sourceware.org/gdb/wiki/FortranVLA
particularly the branch jankratochvil/vla of git://sourceware.org/git/archer.git
Jan
next prev parent reply other threads:[~2013-07-05 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 18:41 Rouslan Korneychuk
2013-07-05 19:08 ` Jan Kratochvil [this message]
2013-07-05 19:27 ` Rouslan Korneychuk
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=20130705190844.GA1296@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=rouslank@msn.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