From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-43137-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 9775 invoked by alias); 2 Mar 2006 22:25:52 -0000
Received: (qmail 9763 invoked by uid 22791); 2 Mar 2006 22:25:51 -0000
X-Spam-Check-By: sourceware.org
Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17)     by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 02 Mar 2006 22:25:49 +0000
Received: from drow by nevyn.them.org with local (Exim 4.54) 	id 1FEwEy-0005Ye-0b; Thu, 02 Mar 2006 17:25:44 -0500
Date: Thu, 02 Mar 2006 23:02:00 -0000
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
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
Message-ID: <20060302222543.GA21332@nevyn.them.org>
Mail-Followup-To: Mark Kettenis <mark.kettenis@xs4all.nl>, rearnsha@arm.com, 	gdb-patches@sourceware.org, sjackman@gmail.com
References: <20060220214918.GA28798@nevyn.them.org> <1140519913.27380.29.camel@pc960.cambridge.arm.com> <20060221153601.GA21183@nevyn.them.org> <20060302221446.GA18830@nevyn.them.org> <200603022222.k22MMQre000048@elgar.sibelius.xs4all.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200603022222.k22MMQre000048@elgar.sibelius.xs4all.nl>
User-Agent: Mutt/1.5.8i
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2006-03/txt/msg00060.txt.bz2

On Thu, Mar 02, 2006 at 11:22:26PM +0100, Mark Kettenis wrote:
> 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?

But... what frame?  Is there a relevant frame?  I don't believe that
there is.  This is used for things like breakpoints and explicit "x/i".
Maybe you see something I don't, though?

Now, I could get it from get_current_frame() instead of read_register,
if you like.

-- 
Daniel Jacobowitz
CodeSourcery