public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/DWARF] Add DW_AT_GNAT_descriptive_type support
Date: Wed, 03 Nov 2010 20:48:00 -0000	[thread overview]
Message-ID: <20101103204844.GB2445@adacore.com> (raw)
In-Reply-To: <20101103192435.GA9182@host0.dyn.jankratochvil.net>

> 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?

Unfortunately not. In order to understand the debugging info, you need
to read the GNAT encoding spec in exp_dbug.ads (in the compiler
sources).

> 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.

We simply do not have the resources, and we don't project to have these
resources any time soon. Also, we are still stuck with stabs for a while,
as we haven't been able to transition to DWARF on some of the platforms
that AdaCore supports (Eg: AIX, Tru64, some versions of LynxOS, HP/UX). 
We've identified some encodings that should be easy to express in pure
DWARF, and these changes are in the queue, but the rest won't be done
any time soon, I'm afraid.

> 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.

I only expect the contributors to do their best: If they notice
some regressions in gdb.ada with their patch, then try seeing if
it's an obvious problem, but otherwise just ask either Paul or myself.
I'm completely overworked these days, but I will always make room
to help out. I understand that the Ada part can be obscure, so
I don't expect more than that. And if someone introduces a regression,
then oh well, I'll notice it eventually, and then go on to fix it.

-- 
Joel

      reply	other threads:[~2010-11-03 20:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091224180657.GV5942@adacore.com>
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
     [not found]         ` <20091225093943.GA25252@host0.dyn.jankratochvil.net>
2010-11-03 19:25           ` Jan Kratochvil
2010-11-03 20:48             ` Joel Brobecker [this message]

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=20101103204844.GB2445@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).