From: David Relson <relson@osagesoftware.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Looking for x86 or AMD64 disassembler
Date: Sat, 5 Dec 2009 21:50:05 -0500 [thread overview]
Message-ID: <20091205215005.7d3133dd@osage.osagesoftware.com> (raw)
In-Reply-To: <1260062990.26276.12.camel@mercury>
On Sat, 05 Dec 2009 18:29:50 -0700
Brandon Vargo wrote:
> On Sat, 2009-12-05 at 19:33 -0500, David Relson wrote:
> > I'm looking for a disassembler so that I can see the underlying
> > assembly code in a variety of files, for example elf executables,
> > DOS executables, binary files (such as the master boot record
> > (MBR)), etc.
> [snip]
> > What do you all recommend for disassemblers? Are there any good
> > ones for Gentoo?
>
> I've used objdump (part of binutils) in the past for looking at ELF
> files; look at the -d option for disassembly. A quick test shows that
> it seems to work for exe files too, but I've never used it that way
> as I don't use Windows much, so I don't know for sure.
>
> For the MBR, I don't know of any disassemblers per-se, but hex editors
> work well depending on what you are doing. hexdump (part of
> sys-apps/util-linux) works well. You might want to make an image of
> the MBR first with dd, depending on which tool you use, as some do not
> support reading from the disk directly.
>
> Regards,
>
> Brandon Vargo
>
Hi Brandon,
Indeed, hexdump mbr would show me the bytes but I want to see the code
as instructions.
objdump works fine for ELF. Being greedy, the ideal tool would handle
all 3 formats.
The immediate need is pure binary (like the MBR). A couple of weeks
ago I had to resort to an old DOS disassembler for a DOS executable.
I'd be much happier with a straight Linux solution.
Regards,
David
next prev parent reply other threads:[~2009-12-06 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 0:33 [gentoo-user] Looking for x86 or AMD64 disassembler David Relson
2009-12-06 1:29 ` Brandon Vargo
2009-12-06 2:50 ` David Relson [this message]
2009-12-06 12:41 ` Robin Atwood
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=20091205215005.7d3133dd@osage.osagesoftware.com \
--to=relson@osagesoftware.com \
--cc=gentoo-user@lists.gentoo.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