From: Ian Lance Taylor <ian@wasabisystems.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: GDB using addr2line?
Date: Fri, 07 May 2004 22:04:00 -0000 [thread overview]
Message-ID: <m3pt9fvqpv.fsf@gossamer.airs.com> (raw)
In-Reply-To: <409BDEB7.6070005@gnu.org>
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
next prev parent reply other threads:[~2004-05-07 22:04 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 [this message]
2004-05-07 22:40 ` Paul Gilliam
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=m3pt9fvqpv.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=binutils@sources.redhat.com \
--cc=cagney@gnu.org \
--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