Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.compilers    |    Compiler construction, theory, etc. (Mod    |    2,753 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,479 of 2,753    |
|    rlunger to All    |
|    Re: Writing a disassembler ?    |
|    18 Oct 08 01:37:06    |
      From: ryanlunger@gmail.com              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              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca