From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30855 invoked by alias); 31 May 2007 17:24:08 -0000 Received: (qmail 30840 invoked by uid 22791); 31 May 2007 17:24:07 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 31 May 2007 17:24:06 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id A2609982DF for ; Thu, 31 May 2007 17:24:04 +0000 (GMT) Received: from localhost.localdomain (nc-71-2-221-6.dyn.embarqhsd.net [71.2.221.6]) by nan.false.org (Postfix) with ESMTP id 746F7982DD for ; Thu, 31 May 2007 17:24:04 +0000 (GMT) Received: by localhost.localdomain (Postfix, from userid 1000) id 3D71717762E; Thu, 31 May 2007 13:24:04 -0400 (EDT) Resent-From: drow@false.org Resent-Date: Thu, 31 May 2007 13:24:04 -0400 Resent-Message-ID: <20070531172404.GL23651@localhost.localdomain> Resent-To: gdb-patches@sourceware.org Date: Thu, 31 May 2007 17:35:00 -0000 From: Daniel Jacobowitz To: Kalpana Ramamurthy Cc: gdb-patches@sources.redhat.com Subject: Re: Why is the state of cache being changed by regcache_observer_notify_target() ? Message-ID: <20070529133752.GA20950@localhost.localdomain> Mail-Followup-To: Kalpana Ramamurthy , gdb-patches@sources.redhat.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-05/txt/msg00439.txt.bz2 On Tue, May 29, 2007 at 12:12:50PM +0000, Kalpana Ramamurthy wrote: > Why is the regcache_observer_target_changed() changing the values of > register_valid_p as soon as its set earlier ? In case changing one register causes another to change in some unpredictable way. The register should be written to the target when it is changed, and then later read back with the new value. -- Daniel Jacobowitz CodeSourcery