From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Michael Haupt <michael.haupt@oracle.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: debugging custom array types
Date: Thu, 14 Feb 2013 13:44:00 -0000 [thread overview]
Message-ID: <20130214134402.GA19093@host2.jankratochvil.net> (raw)
In-Reply-To: <E76E7F02-2BA5-40F9-BFCC-152151D40201@oracle.com>
On Thu, 14 Feb 2013 14:37:56 +0100, Michael Haupt wrote:
> Am 13.02.2013 um 18:58 schrieb Jan Kratochvil <jan.kratochvil@redhat.com>:
> > That DW_TAG_array_type/DW_TAG_subrange_type with dynamic DW_AT_upper_bound
> > should be supported but not as a directly embedded part of struct.
>
> if I'm not totally mistaken (which I would not preclude), Appendix D.2.1 of
> the DWARF standard document suggests otherwise.
Yes, the example from Appendix D.2.1 is not supported by
archer-jankratochvil-vla.
Jan
next prev parent reply other threads:[~2013-02-14 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 16:51 Michael Haupt
2013-02-11 17:02 ` Jan Kratochvil
2013-02-13 10:50 ` Michael Haupt
2013-02-13 17:52 ` Tom Tromey
2013-02-14 13:27 ` Michael Haupt
2013-02-14 16:51 ` Tom Tromey
2013-02-13 17:59 ` Jan Kratochvil
2013-02-14 13:37 ` Michael Haupt
2013-02-14 13:44 ` Jan Kratochvil [this message]
2013-02-12 19:28 ` Tom Tromey
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=20130214134402.GA19093@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=michael.haupt@oracle.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