Re: Writing a disassembler ?

rlunger <ryanlunger@gmail.com>
Sat, 18 Oct 2008 01:37:06 -0700 (PDT)

          From comp.compilers
Related articles
[3 earlier articles]
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)
| List of all articles for this month |
From: rlunger <ryanlunger@gmail.com>
Newsgroups: comp.compilers
Date: Sat, 18 Oct 2008 01:37:06 -0700 (PDT)
Organization: Compilers Central
References: 08-10-011 08-10-028
Keywords: disassemble
Posted-Date: 18 Oct 2008 19:57:10 EDT

FFU is For Future Use (or Far From Us). Yes, x86 opcodes can be
complex, as has been pointed out, but I do believe that it is also the
most widely used set of processors we have ever seen, so writing a
disassembler for the architecture has it's uses. I've found that the
simplest ways of making something work is the best way (I wrote a
disassembler in QuickBASIC a long time ago). Since the hardest part
of your problem is recognizing the opcodes, start there and then worry
about what to do with your data, how to store it or represent it. Do
what feels right with it, and if that doesn't work, try something
else.


Regards,


R. Lunger


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.