From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13345 invoked by alias); 8 Apr 2003 21:03:39 -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 13338 invoked from network); 8 Apr 2003 21:03:37 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 8 Apr 2003 21:03:37 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id D2C022B23; Tue, 8 Apr 2003 17:03:27 -0400 (EDT) Message-ID: <3E93391F.2050005@redhat.com> Date: Tue, 08 Apr 2003 21:03:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexandre Oliva Cc: gdb-patches@sources.redhat.com Subject: Re: use MIPS NewABI register names when disassembling NewABI code References: <3E927BCA.1080702@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-04/txt/msg00135.txt.bz2 > On Apr 8, 2003, Andrew Cagney wrote: > > >> Ugly? This bit: > >>> + static asymbol *symbols = NULL; > >> is wrong. There is more than one instance of an architecture. > > > Uh. I see. So much for trying to get rid of one more call to > bfd_alloc. This is easy to fix, though. What about the problem of lifetimes? >> How does objdump manage to correctly disassemble something like an >> srecord? > > > Presumably, it doesn't. If it's not an ELF bfd, it has no way to tell > which ABI to disassemble for. Fixing that will cause the gdb side of this problem to fall out. GDB can then wiggle knobs very similar to what the user running objdump would be playing with. See ARM and i386. Andrew