Re: libopcodes counterpart
From: wasatchRiver (wasatchRiver_at_comcast.net)
Date: 09/24/04
- Next message: Yazid: "Re: What did suse9.1 do to my hard disk?"
- Previous message: Lew Pitcher: "Re: octet vs. byte"
- In reply to: Dances With Crows: "Re: libopcodes counterpart"
- Next in thread: Dances With Crows: "Re: libopcodes counterpart"
- Reply: Dances With Crows: "Re: libopcodes counterpart"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 24 Sep 2004 09:47:16 -0700
Basically I am wanting to translate assembly into machine code and
then view it as shellcode without the extra overhead of fully
assembling the buffer (I am assuming that gas is a multi pass
assembler... but that may be a flawed assumption), but I don't want to
re-invent the wheel by rewriting an existing parser. I need multi
platform compatibility and the ability to parse either AT&T or IBM
assembly. I have been poking around in the source code for gas trying
to find the specific functions that parse the buffers and do the
encoding but so far I haven't found the function(s) that I am looking
for.
Currently I have the disassemble functionality working using the
various print_insn_* function calls from dis-asm.h.
I am trying to avoid writing the buffers out (to a file or a file
descriptor), assembling them, then reading them back in but, have
looked at it as a possible solution.
- Next message: Yazid: "Re: What did suse9.1 do to my hard disk?"
- Previous message: Lew Pitcher: "Re: octet vs. byte"
- In reply to: Dances With Crows: "Re: libopcodes counterpart"
- Next in thread: Dances With Crows: "Re: libopcodes counterpart"
- Reply: Dances With Crows: "Re: libopcodes counterpart"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
