Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/DWARF] Add DW_AT_GNAT_descriptive_type support
Date: Wed, 03 Nov 2010 19:25:00 -0000	[thread overview]
Message-ID: <20101103192435.GA9182@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20100112055258.GJ2007@adacore.com> <20091225093943.GA25252@host0.dyn.jankratochvil.net>

On Thu, 24 Dec 2009 23:39:43 -1000, Jan Kratochvil wrote:
> There is DW_TAG_array_type(DW_TAG_subrange_type->DW_AT_type) for this purpose
> IMHO.  But yes, you have said it is possible to do it the DWARF way.
> 
> 
> On Fri, 25 Dec 2009 05:06:46 +0100, Joel Brobecker wrote:
> > But this effort seems to be always stalled in favor of other, more urgent
> > ones.  It's an effort that is actually dear to me, since I very much dislike
> > this encoding.
> 
> OK, np, fine with me, fully understood.  I just missed some note about the
> reasons for this patch.


On Mon, 11 Jan 2010 19:52:58 -1000, Joel Brobecker wrote:
> This will be adjusted later on, when support is added to GCC.


The regression today and some recent talk suggested me to revive this thread.

People developing non-Ada GDB code sometimes accidentally cause Ada
regressions but the current Ada debug info (at least as encoded in DWARF) is
unreadable for me, despite I tried.

Is there some Ada-specific `readelf -wi'-like tool to be able to read it?

And why not to implement whole Ada properly in DWARF, with few extensions
proposed at <dwarf-discuss@lists.dwarfstd.org> when/if needed?  As AdaCore
supplies both the compiler and the debugger I see no need to be bound by STABS
you noted before.

As Ada regressions are AFAIK not acceptable for FSF GDB check-ins there should
be a way to make them troubleshootable by non-Ada developers.


Thanks,
Jan


  reply	other threads:[~2010-11-03 19:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-24 18:07 Joel Brobecker
2009-12-24 19:40 ` Jan Kratochvil
2009-12-25  4:36   ` Joel Brobecker
2009-12-25  9:40     ` Jan Kratochvil
2010-11-03 19:25       ` Jan Kratochvil [this message]
2010-11-03 20:48         ` Joel Brobecker
2010-01-05 20:12 ` Tom Tromey
2010-01-11 10:41   ` Joel Brobecker
2010-01-11 18:15     ` Tom Tromey
2010-01-12  5:53       ` Joel Brobecker

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=20101103192435.GA9182@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.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