From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11411 invoked by alias); 8 Jan 2003 19:05:10 -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 11240 invoked from network); 8 Jan 2003 19:04:57 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 209.249.29.67 with SMTP; 8 Jan 2003 19:04:57 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18WNO7-0000Ep-00 for ; Wed, 08 Jan 2003 15:05:23 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18WLVi-0000Cj-00 for ; Wed, 08 Jan 2003 14:05:06 -0500 Date: Wed, 08 Jan 2003 19:05:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: Failures in store.exp caused by regcache Message-ID: <20030108190506.GA558@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i X-SW-Source: 2003-01/txt/msg00086.txt.bz2 (Or rather, by the value code's interaction with the regcache) Andrew, this is more your area; I'd like your advice before I dig any further. Here's what's going wrong. Consider the command sequence: "up; print u; set u = s_1; print u". - u has class LOC_REGISTER - The register's home is memory - read_var_value therefore returns an lval_memory - the value of the register is in the register unwind cache at this point - we modify the memory backing the store - we have no way to tell that we've just modified the value of a saved register on the stack - the second print returns the cached value So, what do we do? I really don't want to flush cached register values in value_assign. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer