Re: Disassembling mostly-unknown data

[Thiemo Seufer <ths at networkno dot de>]

Chris Boot wrote:
> David Daney wrote:
> >Chris Boot wrote:
> >
> >>
> >>*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. :-/
> >>
> >
> >Something like:
> >
> >objdump -s --target=binary
> >
> >David Daney
> 
> Hmm, that just gives me the data without the instructions, and adding -D 
> just makes objdump show one thing then the next. Never mind, time for 
> some PERL I think.
> 
> Now, how about the issue of MIPS-16 instructions? Should objdump detect 
> these automatically (in which case I don't have any) or do I need to do 
> something special? I know I should be able to tell by looking at the 
> j/jal/etc... instructions to see if they jump to an odd address, but I 
> don't even know if that particular instruction is valid...
> 
> More particularly, is there a way of telling objdump what ISAs it can 
> and can't use? For example, I know my CPU doesn't have certain 
> instructions, so can I have them not appear or be interpreted 
> differently should the need arise?

objdump --help suggests "objdump -mmips:isa32" etc.


Thiemo