From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1839 invoked by alias); 15 Jul 2003 22:29:17 -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 1832 invoked from network); 15 Jul 2003 22:29:17 -0000 Received: from unknown (HELO neon-gw.transmeta.com) (63.209.4.196) by sources.redhat.com with SMTP; 15 Jul 2003 22:29:17 -0000 Received: (from root@localhost) by neon-gw.transmeta.com (8.9.3/8.9.3) id PAA18878; Tue, 15 Jul 2003 15:29:11 -0700 Received: from mailhost.transmeta.com(10.1.1.15) by neon-gw.transmeta.com via smap (V2.1) id xma018864; Tue, 15 Jul 03 15:28:47 -0700 Received: from casey.transmeta.com (casey.transmeta.com [10.10.25.22]) by deepthought.transmeta.com (8.11.6/8.11.6) with ESMTP id h6FMSoF07805; Tue, 15 Jul 2003 15:28:50 -0700 (PDT) Received: (from dje@localhost) by casey.transmeta.com (8.9.3/8.7.3) id PAA29071; Tue, 15 Jul 2003 15:28:50 -0700 From: Doug Evans MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16148.32802.626837.445502@casey.transmeta.com> Date: Tue, 15 Jul 2003 22:29:00 -0000 To: Daniel Jacobowitz Cc: gdb@sources.redhat.com Subject: RFC: Unpredictable register set operations In-Reply-To: <20030715220923.GA30513@nevyn.them.org> References: <20030715220923.GA30513@nevyn.them.org> X-SW-Source: 2003-07/txt/msg00178.txt.bz2 Daniel Jacobowitz writes: > So what happens if you "set $ps = 0"? Well, the right thing happens, but > until the next time the target stops "print $ps" will print 0. Which is not > actually the value of the $ps register. > > Thoughts? Is this a problem worth fixing? Definately worth fixing. In complex systems there may be various scripts that make use of these register's values. Having these scripts randomly break because gdb is lying to the script about what the value of the register is is, well, not nice.