From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 383 invoked by alias); 3 Mar 2003 04:50:56 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 376 invoked from network); 3 Mar 2003 04:50:54 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 3 Mar 2003 04:50:54 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18pjnm-0006TJ-00; Mon, 03 Mar 2003 00:51:55 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18phuR-000256-00; Sun, 02 Mar 2003 23:50:39 -0500 Date: Mon, 03 Mar 2003 04:50:00 -0000 From: Daniel Jacobowitz To: Stephane Carrez Cc: Michael Elizabeth Chastain , kettenis@chello.nl, brobecker@gnat.com, gdb@sources.redhat.com Subject: Re: 8-byte register values on a 32-bit machine Message-ID: <20030303045039.GB7933@nevyn.them.org> Mail-Followup-To: Stephane Carrez , Michael Elizabeth Chastain , kettenis@chello.nl, brobecker@gnat.com, gdb@sources.redhat.com References: <200303020651.h226px701731@duracef.shout.net> <3E61D045.1040000@nerim.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E61D045.1040000@nerim.fr> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-03/txt/msg00040.txt.bz2 On Sun, Mar 02, 2003 at 10:35:01AM +0100, Stephane Carrez wrote: > Hi! > > Michael Elizabeth Chastain wrote: > > >[...] > >Anyways, I think there are two problems here: > > > >(1) dwarf2_evaluate_loc_desc is getting called with ctx->in_reg=true > > and size=8. I need to provide an actual test executable to show > > this happening. When this happens, dwarf2_evaluate_loc_desc just > > reads *1* register. This is definitely wrong (if my description > > of gdb's behavior is accurate). > > > > > clap! clap! clap! > > FYI, I have this problem too with HC11 and it is *critical* for me as > this platform being a 16-bit register target, it uses multiple registers > quite intensively (up to 4 for long long). It was working very very well > before... OK, so we need to do something about this before the next release. It's a problem I hadn't anticipated. I have several ideas on how to progress, particularly: - Making a call to the LOC_COMPUTED functions return a LOC_REGISTER so that the logic in read_var_value can go back to handling this case. - Implement the get-next-register mechanism that Mark K. designed. Hmm, for the former I'm not sure I know what I want it to look like yet; but some logic definitely needs to be pushed higher than it is (i.e. out of the evaluator). -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer