This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: Disassembling mostly-unknown data
- From: Chris Boot <bootc at bootc dot net>
- To: David Daney <ddaney at avtrex dot com>
- Cc: binutils at sourceware dot org
- Date: Fri, 21 Oct 2005 20:35:17 +0100
- Subject: Re: Disassembling mostly-unknown data
- References: <4359396C.1030502@bootc.net> <43593CE8.3050802@avtrex.com> <43593DA2.4060202@avtrex.com>
David Daney wrote:
David Daney wrote:
Chris Boot wrote:
Hi all,
I'm having difficulty getting my head around the documentation
regarding a particular special case I'm facing: I have a binary
firmware image that I need to disassemble portions of. I know the CPU
architecture (it's a MIPS) and ISA and all, but the binary image
isn't in any format that binutils recognises, or that I even know (so
I can't just add the binary format to bfd).
Ideally what I'd like to be able to do is have output similar to
'hexdump -C <file>', but with an added column containing the
instruction that may (or may not) be at that particular address.
Fortunately for me MIPS has a fixed instruction size of 32 bits
although I suspect I may have to play with MIPS-16 at some point
(thus, 16-bit instructions).
Would anyone be able to provide me with guidance pulling off such a
tool?
Something like mipsel-linux-objdump -D --target=binary
--architecture=mips
Sorry I meant to send to the list as well. So I am resending.
David Daney.
*smacks head hard against a wall repeatedly*
Thank you.
Now, can I get some ASCII text as well? I'd rather not be misled into
believing something is an instruction when it's actually text... Maybe I
should write a PERL script to do this. :-/
Thanks again,
Chris
PS: I really should pay more attention, I did the same and didn't post
to the list.
--
Chris Boot
bootc@bootc.net
http://www.bootc.net/