From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13287 invoked by alias); 18 Aug 2002 16:42:29 -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 13280 invoked from network); 18 Aug 2002 16:42:28 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by sources.redhat.com with SMTP; 18 Aug 2002 16:42:28 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id F22363CFA; Sun, 18 Aug 2002 12:42:18 -0400 (EDT) Message-ID: <3D5FCE6A.9080308@ges.redhat.com> Date: Sun, 18 Aug 2002 09:42:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020810 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Jason R Thorpe , gdb-patches@sources.redhat.com Subject: Re: [patch/rfc] Don't complain about unknown OSABI References: <3D5FC00D.50001@ges.redhat.com> <20020818154927.GA20358@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00505.txt.bz2 > On Sun, Aug 18, 2002 at 11:41:01AM -0400, Andrew Cagney wrote: > >> Hello, >> >> The attached patch removes the warning message that is printed when the >> OSABI is unknown (all the sniffers failed). >> >> When debugging an embedded executable, there is no OSABI info. Hence I >> don't think the warning should be issued. This can be seen when >> debugging a GCC created, mips-elf executable. >> >> thoughts? >> Andrew > > > I like it. I asked for this change about two months ago when I noticed > it on mips-elf. And there's a typo in the message you're removing, > too. > [On the related hand, we just had some reports about a case where the OS > ABI is isn't detected (on uClibc) - do you think a (configure.tgt based > or *.mt based rather than in a header, I think) way to specify the > default OS ABI based on the target triplet would be appropriate? I know. Being able to print the OSABI would help (set/show abi). I think it should ask BFD. BFD can then go and look at the target tuple. That would mean that BFD and GDB are ``on the same page''. See the hacks I've got GDB pulling to figure out the default architecture. > Linux kernels do not have ABI tagging, which comes from glibc, but > generally use the Linux OS ABI.] Andrew