From: Eli Zaretskii <eliz@gnu.org>
To: Jim Blandy <jimb@codesourcery.com>,
julian@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Accept DWARF 3-format debug info
Date: Fri, 09 Jun 2006 16:42:00 -0000 [thread overview]
Message-ID: <uslmeqo19.fsf@gnu.org> (raw)
In-Reply-To: <20060609122532.GA24240@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 9 Jun 2006 08:25:33 -0400)
> Date: Fri, 9 Jun 2006 08:25:33 -0400
> From: Daniel Jacobowitz <dan@codesourcery.com>
> Cc: Jim Blandy <jimb@codesourcery.com>, julian@codesourcery.com,
> gdb-patches@sourceware.org
>
> On Fri, Jun 09, 2006 at 10:28:07AM +0300, Eli Zaretskii wrote:
> > 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).
>
> Same thing that happens when we see a DWARF-2 feature we don't support
> ;-)
Which is -- what? (I really don't know.)
> GCC is actually a DWARF-3 producer in almost all ways. It just didn't
> bump the version number, to avoid upsetting consumers, since most of
> the changes are forwards-compatible.
Well, the same reasons GCC had to avoid upsetting consumers might be
relevant for us as well, don't you think?
next prev parent reply other threads:[~2006-06-09 16:42 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 [this message]
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=uslmeqo19.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--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