From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6794 invoked by alias); 7 Aug 2004 18:31:48 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 6784 invoked from network); 7 Aug 2004 18:31:47 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 7 Aug 2004 18:31:47 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i77IVle1000516 for ; Sat, 7 Aug 2004 14:31:47 -0400 Received: from zenia.home.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i77IVja23477; Sat, 7 Aug 2004 14:31:46 -0400 To: Andrew Cagney Cc: Ian Lance Taylor , "Nathan J. Williams" , gdb-patches@sources.redhat.com Subject: Re: RFA: assert that target_fetch_registers did its job References: <4114FF92.7000300@gnu.org> From: Jim Blandy Date: Sat, 07 Aug 2004 18:31:00 -0000 In-Reply-To: <4114FF92.7000300@gnu.org> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-08/txt/msg00212.txt.bz2 Andrew Cagney writes: > I'll disable this while we sort things out. I've just hit another > system (PPC/NetBSD) that panics. > > While requiring that the inferior always `supply' a register appears > reasonable (and I agree with the theory) it turns out we don't have > the mechanisms for indicating all the possible supplied register > states (see below) and the implementors of the supply code didn't > realise that was part of the contract :-( > > I think we can also just as effectively (and not as fatally :-) use > the testsuite and something based on ``maint print cooked-registers'' > (it will need to print state info) to detect mis-behaving inferior > code. Yeah, I think this is probably best. I hadn't expected this much unravelling when I tugged on that little thread. :) It seems pretty clear that some of the consumers of register contents need to become more sophisticated. But that will necessarily be a more gradual process.