From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA v2] valprint.c / *-valprint.c: Don't lose `embedded_offset'
Date: Mon, 24 Jan 2011 21:06:00 -0000 [thread overview]
Message-ID: <20110124205926.GB2413@adacore.com> (raw)
In-Reply-To: <201101241910.55018.pedro@codesourcery.com>
> Ah, so you're saying that most of the failures we get with FSF
> gnat are related to some sort descriptive-type debug info support
> or something like that, I guess?
It's a little more involved than that, and I can't really claim that
I understand all the issues, but basically, we have a bunch of changes
that improve the quality of the debugging information. But they depend
on the descriptive-type stuff. For us to be able to improve things in
the short term, we need that one patch to go in first... I do understand
that the patch is not getting a lot of enthusiasm, but failing that,
we're going to have to wait for AdaCore's long-term interest in moving
to standard DWARF.
--
Joel
next prev parent reply other threads:[~2011-01-24 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 13:24 Pedro Alves
2011-01-24 16:56 ` Pedro Alves
2011-01-24 17:37 ` Joel Brobecker
2011-01-24 19:39 ` Pedro Alves
2011-01-24 19:46 ` Pedro Alves
2011-01-24 21:06 ` Joel Brobecker [this message]
2011-01-24 19:47 ` Pedro Alves
2011-01-28 11:35 ` 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=20110124205926.GB2413@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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