This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Difference between objdump and readlelf output

From: Nick Clifton <nickc at redhat dot com>
To: Tiron Adrian <tiron_adrian at yahoo dot com>, binutils at sourceware dot org
Date: Thu, 04 Jan 2007 13:40:11 +0000
Subject: Re: Difference between objdump and readlelf output
References: <20070104114101.81894.qmail@web58315.mail.re3.yahoo.com> <20070104125137.GA12887@bubble.grove.modra.org>

Hi Alan,

readelf -x is broken for little-endian.   I don't think readelf should
be trying to print the value of each 32-bit word.  After all, the
section data may well not be 32-bit words, especially on 64-bit
targets.  Instead we should just dump the bytes, with an extra space
every 4 bytes to help in counting bytes.

Does anyone think we should be doing something different?

Makes sense to me.

Cheers
  Nick

References:
- Difference between objdump and readlelf output
  - From: Tiron Adrian
- Re: Difference between objdump and readlelf output
  - From: Alan Modra

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]