From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11809 invoked by alias); 21 Jul 2003 20:33:25 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 11796 invoked from network); 21 Jul 2003 20:33:24 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 21 Jul 2003 20:33:24 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 5FD112B7F; Mon, 21 Jul 2003 16:33:24 -0400 (EDT) Message-ID: <3F1C4E14.6050007@redhat.com> Date: Mon, 21 Jul 2003 20:33: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: Nick Clifton Cc: Jim Blandy , gdb@sources.redhat.com, binutils@sources.redhat.com Subject: Re: What to do with info addr and location expressions References: <16152.3014.959070.885970@localhost.redhat.com> <20030718153016.GA17382@nevyn.them.org> <3F18175E.30607@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-07/txt/msg00275.txt.bz2 > Hi Jim, > > >>> One thing though - readelf does not, and should not, used the bfd >>> library. One of its main goals is to provide an alternative to bfd >>> for parsing and displaying ELF files, so that it can act as a >>> sanity/bug check. > >> >> The natural home for such code would be a libdwarf, but we don't have >> that yet. In the the mean time, could the code live in libiberty, >> like the demangler? > > > I do not think that this is really suitable for libiberty. > > The simplest method would be to break the code out into a separate > file that lives in the binutils/ directory and which could then be > compiled into either readelf or gdb. That would mean bundling the binutils directory in with GDB. Hmm ... Andrew