Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Cary Coutant <ccoutant@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Add support for DW_LNE_set_discriminator
Date: Tue, 09 Jun 2009 23:59:00 -0000	[thread overview]
Message-ID: <m34ouphsbk.fsf@fleche.redhat.com> (raw)
In-Reply-To: <c17be2b30906091422j7e3cf6a1m50756feeef7af68a@mail.gmail.com> (Cary Coutant's message of "Tue\, 9 Jun 2009 17\:22\:35 -0400")

>>>>> "Cary" == Cary Coutant <ccoutant@google.com> writes:

Cary> One question, though. I've written the patch to maintain the
Cary> philosophy that gdb will complain about any unknown extended opcodes,
Cary> and will give up on processing the remainder of the line number table.
Cary> I could change default case in dwarf_decode_lines() to just skip over
Cary> unknown extended opcodes, instead of adding the explicit case for the
Cary> one new opcode. Which would be preferable?

I think the current approach seems reasonable.  If someone adds a
semantics-changing opcode, it seems preferable to fail than to get the
wrong answer.  But, I'm not very well versed in the ins and outs of
dwarf interpretation...

Right now the complaint does not mention the unrecognized opcode or
anything like that.  It seems like that would be a nice addition.

Cary> * dwarf2read.c (dwarf_decode_lines): Recognize and ignore
Cary> DW_LNE_set_discriminator.

Ok.  For future reference, a link to the standard proposal would have
helped :)

Tom


  reply	other threads:[~2009-06-09 23:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 21:22 Cary Coutant
2009-06-09 23:59 ` Tom Tromey [this message]
2009-06-10 14:03   ` Cary Coutant
2009-06-10 14:36     ` 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=m34ouphsbk.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=ccoutant@google.com \
    --cc=gdb-patches@sourceware.org \
    /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