This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
i386 struct disassemble_info
- From: "Lucian Adrian Grijincu" <lucian dot grijincu at gmail dot com>
- To: binutils at sourceware dot org
- Date: Mon, 26 Feb 2007 10:16:58 +0200
- Subject: i386 struct disassemble_info
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=RAiFWCRaroj2ADTjgoOVoNggJ1pwFgUpK3Sz9w541AxULxLldy7aiIzqaPitwoyotTF6+qdj9oAh3CPeDrzVtuGmuNalr8uZIMItKjpHOUyaNOROgple7i8uQrL6O7RPJy6Bjcbj36Wjnr8XNTbMyQ0KeflhwkWaAN76nHMT8fY=
- Reply-to: lucian dot grijincu at gmail dot com
Hello,
A project I'm working on needs to get all function calls from an input
object file.
I've managed to get a simple program to print to stdout all the
disassembled code but there's an issue regarding struct
disassemble_info.
Some of it's fields are not completed when I disassemble an
instruction on i386 but are completed for other architectures (sparc
for example).
The one I'm most interested is insn_type.
I've looked over the source of binutils/opcodes and could not find a
way to determine the type of the currently disassembled instruction
other than to redirect the string representation of the instruction to
some place, parse it and look for "call WHATEVER" types of strings.
I would like to know if there is a more straight forward & PORTABLE
way to do this.
If not I'd have to create a parser for every type of ASM syntax
supported by libopcodes (this means AT&T and Intel for i386, but
there's more to it than i386).
PS: if there's a libopcodes "tutorial" out there plese point me to it.
--
Thank you,
Lucian Adrian Grijincu