This is the mail archive of the binutils@sources.redhat.com 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]

Sparc -> x86 target


Hi all,
I've got a strange problem. I'm trying to develop a software
that does cross-analisys of assembly code from one platform
to another. As example, I am actually able to run it on
MIPS32->AlphaAXP,MIPS32,SPARC,x86
SPARC->AlphaAXP,MIPS32,SPARC
AlphaAXP->AlphaAXP,MIPS32,SPARC,x86
x86->AlphaAXP,MIPS32,SPARC,x86

All the previous analyzers works correctly. I have a problem
during code analisys when running on Sparc and targetting x86.
I don't know if it's a bug in my code or in binutils (libbfd/libopcodes)

code, but it's happening only in the above said "porting", in
binutils-land
code. I analyzed the core dump and it happens into the i386-dis.
disassembly
function into the print_i386_insn function during a test about 32 or 64
bit mode
of the target platform. The binary file I'm analyzing is a copy of a
working ethereal
binary, and is the same test used in all the other "platforms". I didn't
use any strange
parameter to invoke the disassembly function, and the cross-built
binutils works
flawlessly (I can dump the binary with objdump on the Sparc system). Are
there any
tricks, suggestions  or issues I'm not aware of ?

Thanks a lot
Gilberto



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