From: Daniel Jacobowitz <drow@false.org>
To: binutils@sourceware.org
Subject: Re: PATCH: PR binutils/4756: addr2line fails on relocatable linux kernel
Date: Mon, 09 Jul 2007 19:52:00 -0000 [thread overview]
Message-ID: <20070709185604.GA23863@caradoc.them.org> (raw)
In-Reply-To: <20070709184340.GA14140@lucon.org>
On Mon, Jul 09, 2007 at 11:43:40AM -0700, H.J. Lu wrote:
> bfd_simple_get_relocated_section_content shouldn't apply relocations
> on executable and shared library with relocations. This patch uses
> the same check in binutils/objdump.c.
Do you see any way to fix this that does not drop support for shared
libraries where debug info has not been relocated?
I don't think so, and I do not object to your patch. But this
function was originally added for shared libraries, not for ET_REL
objects. I'm sure you remember the several different ways binutils
treated relocations in shared library debug info over time.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-07-09 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 18:56 H.J. Lu
2007-07-09 19:52 ` Daniel Jacobowitz [this message]
2007-07-09 20:00 ` H.J. Lu
2007-07-09 21:30 ` Daniel Jacobowitz
2007-07-10 10:55 ` Nick Clifton
2007-07-10 14:05 ` Alan Modra
2007-07-10 14:18 ` H.J. Lu
2007-07-10 16:37 ` Alan Modra
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=20070709185604.GA23863@caradoc.them.org \
--to=drow@false.org \
--cc=binutils@sourceware.org \
/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).