From: Daniel Jacobowitz <drow@mvista.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Joern Rennecke <joern.rennecke@superh.com>,
hjl@gnu.org, binutils@sources.redhat.com
Subject: Re: RFA: Fix readelf -wi test (Was: Re: readelf: apply all rela relocations in the debug_info section)
Date: Sat, 26 Apr 2003 13:56:00 -0000 [thread overview]
Message-ID: <20030426135644.GA31292@nevyn.them.org> (raw)
In-Reply-To: <m3of2thew4.fsf@localhost.localdomain>
On Sat, Apr 26, 2003 at 08:55:07AM +0100, Nick Clifton wrote:
> Hi Daniel,Hi Joern,
>
> > > > + ".*DW_AT_producer.*(GNU C|indirect string).*"
> > > > + ".*DW_AT_language.*ANSI C.*"
> > > > + ".*DW_AT_name.*(testprog.c|indirect string).*"
> > > > + ".*DW_AT_name.*fn.*"
> > > > + ".*DW_AT_name.*(main|indirect string).*"
> > > > + }
> > >
> > > At least for sh-elf, after the " \(indirect string, offset: 0x[0-9a-f]+\): "
> > > bit, it still displays the original string. Are there any targets where
> > > this is not the case?
> >
> > There should not be; if there are, it's a bug. So I'd say the indirect
> > string bit can probably go.
>
> Actually they are needed. Without them the sh-elf sh64-elf and
> mn10300-elf ports will fail this test. The problem is that we are
> running readelf on the object file not the executable, so there can be
> unresolved relocs in the debug info sections.
I'm confused. Remember the original subject of this thread? I thought
we should be applying all unresolved relocations now.
> Anyway I have added this line to the test and checked it in.
Thanks!
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-04-26 13:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 18:28 readelf: apply all rela relocations in the debug_info section Joern Rennecke
2003-04-22 18:36 ` Joern Rennecke
2003-04-22 20:13 ` RFA: Fix readelf -wi test (Was: Re: readelf: apply all rela relocations in the debug_info section) Joern Rennecke
2003-04-23 17:36 ` Nick Clifton
2003-04-23 17:39 ` Daniel Jacobowitz
2003-04-23 17:59 ` Nick Clifton
2003-04-23 18:09 ` H. J. Lu
2003-04-23 18:17 ` Nick Clifton
2003-04-23 18:22 ` H. J. Lu
2003-04-23 18:47 ` Joern Rennecke
2003-04-24 17:21 ` Joern Rennecke
2003-04-25 9:34 ` Nick Clifton
2003-04-25 13:38 ` Daniel Jacobowitz
2003-04-25 15:36 ` H. J. Lu
2003-04-25 16:05 ` Nick Clifton
2003-04-25 16:10 ` H. J. Lu
2003-04-25 16:43 ` Joern Rennecke
2003-04-25 17:18 ` Daniel Jacobowitz
2003-04-26 7:57 ` Nick Clifton
2003-04-26 13:56 ` Daniel Jacobowitz [this message]
2003-04-27 9:12 ` Nick Clifton
2003-04-28 13:02 ` Joern Rennecke
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=20030426135644.GA31292@nevyn.them.org \
--to=drow@mvista.com \
--cc=binutils@sources.redhat.com \
--cc=hjl@gnu.org \
--cc=joern.rennecke@superh.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).