Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb-patches@sourceware.org,
	Richard Earnshaw <Richard.Earnshaw@arm.com>,
		Shaun Jackman <sjackman@gmail.com>
Subject: Re: RFC: Use the ARM CPSR as a fallback to determine ARM/Thumb
Date: Sun, 26 Feb 2006 13:10:00 -0000	[thread overview]
Message-ID: <20060226054602.GB3330@nevyn.them.org> (raw)
In-Reply-To: <8f2776cb0602242329s1335c677o8a8c1a38314d97c6@mail.gmail.com>

On Fri, Feb 24, 2006 at 11:29:23PM -0800, Jim Blandy wrote:
> If you know which regions of the ROM are thumb and which are ARM, why
> not fake up a .o file that just defines a bunch of symbols --- but
> contains no data --- that map things out for GDB?
> 
> That is, GDB already has range information.  You're just not supplying it.

Because I don't know which regions of the ROM are Thumb and which are
ARM except by executing it.  It's provided by an OS vendor; I don't
even have symbols for it.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2006-02-26  5:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 22:03 Daniel Jacobowitz
2006-02-21 15:36 ` Richard Earnshaw
2006-02-21 16:10   ` Daniel Jacobowitz
2006-03-02 22:23     ` Daniel Jacobowitz
2006-03-02 22:52       ` Mark Kettenis
2006-03-02 23:02         ` Daniel Jacobowitz
2006-03-02 23:10           ` Mark Kettenis
2006-03-02 23:23             ` Daniel Jacobowitz
2008-05-01 18:38       ` Daniel Jacobowitz
2008-05-02 10:17         ` Eli Zaretskii
2008-05-02 14:06           ` Daniel Jacobowitz
2008-05-02 15:47             ` Eli Zaretskii
2008-05-02 16:03               ` Daniel Jacobowitz
2008-05-02 20:34                 ` Eli Zaretskii
2006-02-25 11:12 ` Jim Blandy
2006-02-26 13:10   ` Daniel Jacobowitz [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=20060226054602.GB3330@nevyn.them.org \
    --to=drow@false.org \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@red-bean.com \
    --cc=sjackman@gmail.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