From: Jim Blandy <jimb@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] Detect dwarf address size mismatch
Date: Wed, 11 Jul 2007 20:30:00 -0000 [thread overview]
Message-ID: <m3hcoabs3r.fsf@codesourcery.com> (raw)
In-Reply-To: <20070711194141.GA28114@caradoc.them.org> (Daniel Jacobowitz's message of "Wed, 11 Jul 2007 15:41:41 -0400")
Daniel Jacobowitz <drow@false.org> writes:
> 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.
True. But I think the check should go after the switch in any case;
there's no reason to only apply sanity checking to that one opcode.
But then as long as one's doing that check across all the extended
opcodes, one has the information needed to insulate the surrounding
code from the individual cases' vaguaries.
The first point seems like a definite should-do, unless I'm missing
something; the second one I agree is less clear-cut.
next prev parent reply other threads:[~2007-07-11 20:30 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
2007-07-11 20:30 ` Jim Blandy [this message]
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=m3hcoabs3r.fsf@codesourcery.com \
--to=jimb@codesourcery.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