From: Julian Brown <julian@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jim Blandy <jimb@codesourcery.com>,
gdb-patches@sourceware.org, dan@codesourcery.com
Subject: Re: [PATCH] Accept DWARF 3-format debug info
Date: Fri, 09 Jun 2006 12:39:00 -0000 [thread overview]
Message-ID: <4489670E.40605@codesourcery.com> (raw)
In-Reply-To: <u1wtyss8o.fsf@gnu.org>
Eli Zaretskii wrote:
>>Cc: gdb-patches@sourceware.org, Daniel Jacobowitz <dan@codesourcery.com>
>>From: Jim Blandy <jimb@codesourcery.com>
>>Date: Thu, 08 Jun 2006 16:25:42 -0700
>>
>>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.
>
>
> I agree with the philosophy, but the devil is usually in the
> details...
>
> In this case, what will happen when GDB sees a DWARF-3 feature it
> doesn't yet support? I think we should make sure it displays a
> warning message, instead of throwing an internal error (or some
> similar fatal reaction).
AIUI, the ideal is to just ignore the bits of DWARF which aren't yet
understood, though I don't know how well that works in practice. The
partial-unit case certainly causes unpleasant crashes at present, but
I'd hope that that's an exception rather than a rule. (I, or one of the
other sourcerers, may get to that particular case later.)
Cheers,
Julian
next prev parent reply other threads:[~2006-06-09 12:39 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
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 [this message]
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=4489670E.40605@codesourcery.com \
--to=julian@codesourcery.com \
--cc=dan@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@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