Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Gilliam <gilliam@us.ibm.com>
Cc: binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: GDB using addr2line?
Date: Fri, 07 May 2004 22:40:00 -0000	[thread overview]
Message-ID: <OF799FC643.3C05B95B-ON87256E8D.007C6F16-88256E8D.007C891C@us.ibm.com> (raw)
In-Reply-To: <m3pt9fvqpv.fsf@gossamer.airs.com>

And don't forget ltrace and the like...  they look a lot like a 
special-purpose debugger on the inside.

gdb-owner@sources.redhat.com wrote on 05/07/2004 03:04:44 PM:

> Andrew Cagney <cagney@gnu.org> writes:
> 
> > As anyone looked at (interested in) getting GDB and addr2line sharing
> > common linetable code?  A libsal (source and line) say.
> 
> BFD has long had bfd_find_nearest_line().  It was originally used by
> the linker to report error messages using the source code line--at the
> time, a great innovation.  Ulrich Lauther built addr2line as a wrapper
> around bfd_find_nearest_line().  If you look at addr2line.c, you will
> see that it is very simple.  gdb needs a much more serious approach to
> mapping between addresses and source code lines.
> 
> That said, it would be perfectly reasonable for gdb and addr2line to
> share code, just as it would be perfectly reasonable for gdb and
> objdump/objcopy --debugging to share code.  I don't think anybody has
> looked at either possibility.
> 
> Ian


      reply	other threads:[~2004-05-07 22:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07 20:55 Andrew Cagney
2004-05-07 20:57 ` Daniel Jacobowitz
2004-05-07 22:04 ` Ian Lance Taylor
2004-05-07 22:40   ` Paul Gilliam [this message]

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=OF799FC643.3C05B95B-ON87256E8D.007C6F16-88256E8D.007C891C@us.ibm.com \
    --to=gilliam@us.ibm.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