public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Joern Rennecke <joern.rennecke@superh.com>,
	binutils@sources.redhat.com, Alexandre Oliva <aoliva@redhat.com>,
	Alan Modra <amodra@bigpond.net.au>
Subject: Re: RFA: Fix readelf -wi test (Was: Re: readelf: apply all rela relocations  in the debug_info section)
Date: Wed, 23 Apr 2003 17:39:00 -0000	[thread overview]
Message-ID: <20030423173947.GA29365@nevyn.them.org> (raw)
In-Reply-To: <m3wuhl15js.fsf@localhost.localdomain>

On Wed, Apr 23, 2003 at 06:34:31PM +0100, Nick Clifton wrote:
> Hi Joern,
> 
> > The reaadelf.wi template hasn't been updated in years, and not only
> > the representation of the debug information, even the source file
> > numbers are out of date; that mean that any sucess on this testcase
> > (not counting XFAILs) on any target must have been a bug.
> > I've updated readelf.wi so that the test passes for sh-elf; the readelf.out
> > for sh-elf is attached separately.  The output style change that I have
> > considered a bug is the adding of a trailing "; " in every location
> > expression, e.g. (DW_OP_addr: 0) .
> > The following patch implements this readelf.wi update and suppression of
> > the trailing "; ".
> 
> Your patch still does not resolve the "readelf: Warning: Skipping
> unexpected symbol type 1" problem that you mentioned in your earlier
> post.  In my opinion however the readelf.wi is severely broken, since
> there is no real guaranteed structure to the output of "readelf -wi".
> 
> Instead I am going to apply your patch together with a change of my
> own.  This additional patch:
> 
>   * Filters out "skipping unexpected symbol" messages.

But are they "expected"?  Or are they a bug?  I think they're probably
a bug...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-04-23 17:39 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 [this message]
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
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=20030423173947.GA29365@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=amodra@bigpond.net.au \
    --cc=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --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).