Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: binutils@sourceware.org
Cc: Daniel Jacobowitz <dan@codesourcery.com>,
	 Nick Clifton <nickc@redhat.com>,  Doug Evans <dje@google.com>,
	 dgutson@codesourcery.com,  gdb@sourceware.org
Subject: Re: gdb segv in arm disassembler
Date: Tue, 23 Feb 2010 12:14:00 -0000	[thread overview]
Message-ID: <201002231214.14363.paul@codesourcery.com> (raw)
In-Reply-To: <20100128182736.GA15693@caradoc.them.org>

> * If there are no mapping symbols, default to code using the existing
> legacy search.  This will mishandle recent files iff they have a code
> section containing only literal pools.  Outside of test cases, this
> is unlikely.

IIRC my real-world example for this was interrupt vectors or similar jump 
tables.

Paul


      parent reply	other threads:[~2010-02-23 12:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26  2:23 Doug Evans
2010-01-26  2:37 ` Daniel Jacobowitz
2010-01-28 12:48   ` Nick Clifton
2010-01-28 18:27     ` Daniel Jacobowitz
2010-01-28 19:30       ` Daniel Jacobowitz
2010-01-29 10:21         ` Nick Clifton
2010-02-23 12:14       ` Paul Brook [this message]

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=201002231214.14363.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=binutils@sourceware.org \
    --cc=dan@codesourcery.com \
    --cc=dgutson@codesourcery.com \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=nickc@redhat.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