From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3566 invoked by alias); 11 Nov 2003 18:42:49 -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 3558 invoked from network); 11 Nov 2003 18:42:48 -0000 Received: from unknown (HELO localhost.redhat.com) (216.129.200.20) by sources.redhat.com with SMTP; 11 Nov 2003 18:42:48 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 43C162B8F; Tue, 11 Nov 2003 13:42:46 -0500 (EST) Message-ID: <3FB12DA6.2050201@redhat.com> Date: Tue, 11 Nov 2003 18:42:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: [commit] New function gdbarch_infi_fill References: <3FAED2DE.5000904@gnu.org> <20031110004823.GA7416@nevyn.them.org> <3FAFBA79.9060102@redhat.com> <20031110162644.GA28489@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-11/txt/msg00218.txt.bz2 > Should the assertion: >> >> gdbarch_find_by_info (gdbarch_info (gdbarch)) == gdbarch >> >> always hold? At present architectures like the MIPS make this very hard >> - keying off information found in the BFD and not the corresponding >> info struct. > > > This, however, I'd really like. I remember why I wanted it now. Take > a look at the end of osabi.c:set_osabi - I am not especially confident > that that code works. It seems to me that the above assertion makes it > much more likely to work. Like with "frame_id", it would mean adding some sort of "special" field. That way the MIPS could record that its debugging "o64" but with variation #28: sizeof(long) == 8, FPU :-/ It would also make architecture creation more robust vis: - fill in "gdbarch_info" Setting osabi et.al. based on the bfd et.al. - create the architecture from "gdbarch_info" but with _no_ bfd. harder to get right, but probably more correct. Adding to wish list ... Andrew