Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: gdb@sources.redhat.com
Cc: binutils@sources.redhat.com
Subject: Re: What to do with info addr and location expressions
Date: Tue, 22 Jul 2003 09:20:00 -0000	[thread overview]
Message-ID: <m37k6a6huw.fsf@redhat.com> (raw)
In-Reply-To: <200307212045.h6LKjGld007821@envy.delorie.com> (DJ Delorie's message of "Mon, 21 Jul 2003 16:45:16 -0400")

Hi Guys,

> > Andrew wrote:
> > That would mean bundling the binutils directory in with GDB.  Hmm ...

> DJ replied:
> bfd/ perhaps?

Except that that then ruins the plan that readelf should be buildable
without libbfd.a.

> Doug wrote:
>
> I'd rather not have gdb ship with ./binutils.

OK.
 
> Why not create a new TLD named elf or dwarf or some such and include
> it in binutils and gdb distributions.
> 
> I don't have an opinion on whether one would care whether this particular
> directory has multiple libraries (libelf, libdwarf).
> If one finds that unpalatable, call it dwarf and begin a libdwarf now
> (or whatever).  It needed be all-singing/all-dancing in its first cut.

I would be open to this idea.

Cheers
        Nick
        


  reply	other threads:[~2003-07-22  9:20 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
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 [this message]
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=m37k6a6huw.fsf@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb@sources.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