Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] Detect dwarf address size mismatch
Date: Wed, 11 Jul 2007 19:41:00 -0000	[thread overview]
Message-ID: <20070711194141.GA28114@caradoc.them.org> (raw)
In-Reply-To: <m31wfeoi5a.fsf@codesourcery.com>

On Wed, Jul 11, 2007 at 12:27:29PM -0700, Jim Blandy wrote:
> Would it make sense to move the check after the extended_op switch
> altogether, and always use extended_len to advance line_ptr?  This
> would make GDB more robust against new extended opcodes.

I thought about it; it might make sense to do this in the default
case, but not in any of the handled cases, since they need to advance
line_ptr anyway to read multiple items.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-07-11 19:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 14:19 Daniel Jacobowitz
2007-07-11 19:23 ` Eli Zaretskii
2007-07-11 19:27 ` Jim Blandy
2007-07-11 19:41   ` Daniel Jacobowitz [this message]
2007-07-11 20:30     ` Jim Blandy
2007-07-17 12:52       ` Daniel Jacobowitz
2007-07-17 13:21         ` Mark Kettenis
2007-07-17 13:55           ` Daniel Jacobowitz

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=20070711194141.GA28114@caradoc.them.org \
    --to=drow@false.org \
    --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