From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25270 invoked by alias); 19 Aug 2002 23:19:26 -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 25262 invoked from network); 19 Aug 2002 23:19:25 -0000 Received: from unknown (HELO dr-evil.shagadelic.org) (208.176.2.174) by sources.redhat.com with SMTP; 19 Aug 2002 23:19:25 -0000 Received: by dr-evil.shagadelic.org (Postfix, from userid 7518) id B0B479869; Mon, 19 Aug 2002 16:19:25 -0700 (PDT) Date: Mon, 19 Aug 2002 16:19:00 -0000 From: Jason R Thorpe To: Andrew Cagney Cc: Simon Posnjak , gdb-patches@sources.redhat.com Subject: Re: [PATCH] set osabi command Message-ID: <20020819161925.J2214@dr-evil.shagadelic.org> Mail-Followup-To: Jason R Thorpe , Andrew Cagney , Simon Posnjak , gdb-patches@sources.redhat.com References: <1029446386.30623.13.camel@klada.dyndns.org> <3D6171DA.7000100@ges.redhat.com> <20020819154000.H2214@dr-evil.shagadelic.org> <3D617A9E.7000102@ges.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3D617A9E.7000102@ges.redhat.com>; from ac131313@ges.redhat.com on Mon, Aug 19, 2002 at 07:09:18PM -0400 Organization: Wasabi Systems, Inc. X-SW-Source: 2002-08/txt/msg00567.txt.bz2 On Mon, Aug 19, 2002 at 07:09:18PM -0400, Andrew Cagney wrote: > Are you suggesting that a ``set architecture'' command affect the ``set > osabi'' setting, possibly forcing it to some other value? Yes. > Another option is: > > ... > (gdb) set architecture mips > OSABI arm_eabi_v1 invalid for mips architecture Yah, that's probably good. > and possibly even: > > Force OSABI to ``auto''? (y or n) > > even figuring out that there is a clash is hairy. Actually, figuring out if there is a clash should be easy. Traverse the list of registered OSABIs... each one will have an arch/osabi tuple. If you don't find one that matches the current arch/osabi setting, then you have found a clash, and go into recovery mode. Otherwise, there is no clash, and you can safely use the current osabi setting with the new arch setting. -- -- Jason R. Thorpe