From: Jim Blandy <jimb@codesourcery.com>
To: Julian Brown <julian@codesourcery.com>
Cc: gdb-patches@sourceware.org, Daniel Jacobowitz <dan@codesourcery.com>
Subject: Re: [PATCH] Accept DWARF 3-format debug info
Date: Thu, 08 Jun 2006 23:25:00 -0000 [thread overview]
Message-ID: <vt2wtbrjkll.fsf@theseus.home.> (raw)
In-Reply-To: <4488A920.9090705@codesourcery.com> (Julian Brown's message of "Thu, 08 Jun 2006 23:48:00 +0100")
Julian Brown <julian@codesourcery.com> writes:
> This is part of a series of patches from a CodeSourcery branch which
> enable the output of ARM's RVCT 2.2 compiler to be debugged with gdb.
>
> ARMCC's support for DWARF 3 is superior to its DWARF 2 support, and
> GDB apparently supports much of DWARF 3 already. This patch allows
> DWARF 3 format debug info to be accepted by gdb.
>
> (Some things are notably missing from the DWARF 3 support -- one thing
> I've noticed so far is lack of support for DW_TAG_partial_unit, but
> RVDS 2.2 doesn't seem to need that. A couple of other minor things
> will be addressed in followup patches.)
I think this patch is right. It's true that GDB doesn't support all
of DWARF 3, but GDB's general philosophy is to garner as much
information as it can, and punt the rest, which works well with
DWARF's philosophy. So GDB shouldn't just punt entire compilation
units because they're marked as DWARF 3.
First, please add yourself to the Write After Approval list in
gdb/MAINTAINERS, with an appropriate ChangeLog entry.
Then, go ahead and put in the patch as a separate commit.
Thanks!
next prev parent reply other threads:[~2006-06-08 23:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 22:48 Julian Brown
2006-06-08 23:25 ` Jim Blandy [this message]
2006-06-08 23:59 ` Daniel Jacobowitz
2006-06-18 1:10 ` Mark Kettenis
2006-06-18 4:40 ` Jim Blandy
2006-06-20 19:53 ` RFC: Support DW_FORM_ref_addr as described in DWARF 3 Jim Blandy
2006-07-12 21:21 ` Daniel Jacobowitz
2006-06-09 7:29 ` [PATCH] Accept DWARF 3-format debug info Eli Zaretskii
2006-06-09 12:25 ` Daniel Jacobowitz
2006-06-09 16:42 ` Eli Zaretskii
2006-06-09 17:20 ` Daniel Jacobowitz
2006-06-09 19:46 ` Eli Zaretskii
2006-06-09 12:39 ` Julian Brown
2006-06-09 16:39 ` Eli Zaretskii
2006-06-09 23:18 David Anderson
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=vt2wtbrjkll.fsf@theseus.home. \
--to=jimb@codesourcery.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=julian@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