Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: rearnsha@arm.com, gdb-patches@sourceware.org, sjackman@gmail.com
Subject: Re: RFC: Use the ARM CPSR as a fallback to determine ARM/Thumb
Date: Thu, 02 Mar 2006 22:52:00 -0000	[thread overview]
Message-ID: <200603022222.k22MMQre000048@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060302221446.GA18830@nevyn.them.org> (message from Daniel 	Jacobowitz on Thu, 2 Mar 2006 17:14:46 -0500)

> Date: Thu, 2 Mar 2006 17:14:46 -0500
> From: Daniel Jacobowitz <drow@false.org>
> 
> On Tue, Feb 21, 2006 at 10:36:01AM -0500, Daniel Jacobowitz wrote:
> > What I had in mind for this was:
> > 
> > set arm fallback-mode [arm|thumb|auto]
> > 
> > That is, continue to honor symbol information, but change the fallback
> > when we don't have symbols to arm, thumb, or current cpsr.
> > 
> > And maybe augment that with:
> > 
> > set arm force-mode [arm|thumb|auto]
> > 
> > This would also override symbol information.
> > 
> > This is basically the same as your first option, but spread out over
> > two variables.  How does that sound?
> 
> Something like the attached; look OK?
> 
> For correctness this needs the massive remove_breakpoint patch
> I'm posting next.

Hmm, this really should unwind CPSR from the frame I think.  A bit
impractical to change that now, but something to keep in mind.  Could
you add a FIXME that points this out if you agree?

> 2006-03-02  Daniel Jacobowitz  <dan@codesourcery.com>
> 
> 	* arm-tdep.c (arm_mode_strings, arm_fallback_mode_string)
> 	(arm_force_mode_string, arm_show_fallback_mode)
> 	(arm_show_force_mode): New.
> 	(arm_pc_is_thumb): Honor fallback-mode and force-mode.
> 	Fall back to the CPSR.
> 	(_initialize_arm_tdep): Add "set arm fallback-mode"
> 	and "set arm force-mode".
> 
> 2006-03-02  Daniel Jacobowitz  <dan@codesourcery.com>
> 
> 	* gdb.texinfo (ARM): Document set/show arm fallback-mode
> 	and set/show arm force-mode.
> 


  reply	other threads:[~2006-03-02 22:23 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 [this message]
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

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=200603022222.k22MMQre000048@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=rearnsha@arm.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