From: Daniel Berlin <dberlin@dberlin.org>
To: Nick Clifton <nickc@redhat.com>
Cc: Jim Blandy <jimb@redhat.com>,
gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: What to do with info addr and location expressions
Date: Mon, 21 Jul 2003 20:14:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.56.0307211612350.32098@dberlin.org> (raw)
In-Reply-To: <m3brvnejeb.fsf@redhat.com>
On Mon, 21 Jul 2003, Nick Clifton wrote:
> 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.
I'll go one better (or worse).
Since we don't know the binutils directory will be around when you
compiel gdb, why not make the functions (which are really trivial, and
just large switch statements) static inline, and put them in a
file somewhere in include/, a directory shared by all?
> > Cheers
> Nick
>
>
>
next prev parent reply other threads:[~2003-07-21 20:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 14:54 Elena Zannoni
2003-07-18 15:30 ` Daniel Jacobowitz
2003-07-18 15:50 ` Andrew Cagney
2003-07-21 11:14 ` Nick Clifton
2003-07-21 17:54 ` Jim Blandy
2003-07-21 19:12 ` Andrew Cagney
2003-07-21 20:07 ` Nick Clifton
2003-07-21 20:14 ` Daniel Berlin [this message]
2003-07-21 20:35 ` Doug Evans
2003-07-21 20:33 ` Andrew Cagney
2003-07-21 20:45 ` DJ Delorie
2003-07-22 9:20 ` Nick Clifton
2003-07-22 13:26 ` DJ Delorie
2003-07-22 15:33 ` Nick Clifton
2003-07-22 15:39 ` Daniel Jacobowitz
2003-07-18 16:01 ` Elena Zannoni
2003-07-18 16:11 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.56.0307211612350.32098@dberlin.org \
--to=dberlin@dberlin.org \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=nickc@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).