public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Freeman.Wang@Marconi.com
Cc: binutils@sources.redhat.com
Subject: Re: What's the problem of objdump386?
Date: Wed, 29 Aug 2001 04:32:00 -0000	[thread overview]
Message-ID: <200108291234.f7TCYeP12965@bobsleigh.nickc.cambridge.redhat.com> (raw)
In-Reply-To: <313680C9A886D511A06000204840E1CF6B7ADA@whq-msgusr-02.pit.comms.marconi.com>

Hi Freeman,

: I'm using objdump386(provided with vxWorks 5.4) to disassemble an
: image file. But it seems the information it provided was wrong.

Since you are using a VxWorks product, you probably ought to contact
them directly.  They do provide their own support for these tools.

: Then I tried to  disassemble some object files with it, and found
: some of the files were correctly dumped, but most of them are wrong.

With a problem like this it is very helpful if you can provide an
example of how objdump is failing to disassemble the image.  Also it
really helps if you can provide a *small* reproducible example of the
problem which will let us examine it in detail.

: I guess it's because of some kind of offset which I don't
: know. Could you tell me what's the problem and is there a newer
: version that addresses this problem ?

Without more information we cannot diagnose the problem.  It is likely
however that you do have an old version of the objdump utility.  The
latest release is version 2.11.2.  (Run "objdump386 -v" to find out
which version you have).  You can download the latest sources and
build your own copy by visiting the FSF's FTP site (or one of its
mirrors).

Cheers
	Nick

      reply	other threads:[~2001-08-29  4:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-28 10:23 Wang, Freeman (Xiaoguang)
2001-08-29  4:32 ` Nick Clifton [this message]

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=200108291234.f7TCYeP12965@bobsleigh.nickc.cambridge.redhat.com \
    --to=nickc@redhat.com \
    --cc=Freeman.Wang@Marconi.com \
    --cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).