Related articles |
---|
Writing a disassembler ? lightfault@gmail.com (So and so) (2008-10-10) |
Re: Writing a disassembler ? j.vimal@gmail.com (Vimal) (2008-10-11) |
Re: Writing a disassembler ? jeffrey.kenton@comcast.net (Jeff Kenton) (2008-10-11) |
Re: Writing a disassembler ? DrDiettrich1@aol.com (Hans-Peter Diettrich) (2008-10-11) |
Re: Writing a disassembler ? sh006d3592@blueyonder.co.uk (Stephen Horne) (2008-10-11) |
Re: Writing a disassembler ? ArarghMail810@Arargh.com (2008-10-11) |
Re: Writing a disassembler ? gah@ugcs.caltech.edu (glen herrmannsfeldt) (2008-10-12) |
Re: Writing a disassembler ? lightfault@gmail.com (So and so) (2008-10-16) |
Re: Writing a disassembler ? bc@freeuk.com (Bartc) (2008-10-16) |
Re: Writing a disassembler ? ryanlunger@gmail.com (rlunger) (2008-10-18) |
From: | ArarghMail810@Arargh.com |
Newsgroups: | comp.compilers |
Date: | Sat, 11 Oct 2008 17:32:45 -0500 |
Organization: | Ripco Communications Inc. |
References: | 08-10-011 |
Keywords: | disassemble |
Posted-Date: | 12 Oct 2008 08:19:28 EDT |
On Fri, 10 Oct 2008 16:57:31 +0200, "So and so" <lightfault@gmail.com>
wrote:
>I've set myself a goal to write a disassembler, so far I've managed to
>understand most of Intel's documentation (for now it's only going to
>disassemble x86 code) and I'm about to start writing the basic
>skeleton.
That can be a very non-trivial program. If you intend to limit it to
32-bit flat file types like COFF or ELF, it wouldn't be too bad, as in
those one pretty much knows where the code & where the data is, and
the relocations aren't too bad. If, on the other hand, you intend to
handle the full range fo x86 executable file types, it gets real messy
very quickly.
Just decoding a single instruction is no biggy. I wrote a routine for
that years ago.
> ...
All the rest of your questions are good ones. :-) I don't have the
answers.
--
ArarghMail810 at [drop the 'http://www.' from ->] http://www.arargh.com
BCET Basic Compiler Page: http://www.arargh.com/basic/index.html
Return to the
comp.compilers page.
Search the
comp.compilers archives again.