I tried your advice on Ollydbg and it worked great for me. I was able to assemble a few ADD instructions and get the hex results. Some of them were different than my assembler did it but I could see why. So I just let my assembler alone for now. Right now I am working on the error checking and displaying error messages to the user.
Thanks again so much for this advice. It really hit the spot for me. On Sun, Oct 19, 2008 at 12:37 PM, Gerardo Richarte <[EMAIL PROTECTED]> wrote: > Kjell Godo wrote: > > I have completed the Smalltalk code for the > > picoLARC LambdaLisp Assembler > > for the machine ADD instruction > > > LambdaLisp Assembler looks like > > ( add ( into:From: EAX 5 ) ) > > ( add ( into:From: EAX ( at EBP ) ) ) > > ( add ( into:From: EAX ( at ( + EBP 4 ) ) ) ) > > ( add ( into:From: EAX ( at ( scale:index:base: 4 EBX EBP ) ) ) ) > nice! > > > have OllyDbg > > and WinDbg and I was going to get that other debugger somebody > > mentioned in here somewhere. I don't know which way is best and > > easiest to use. Just to get a hex compilation results listing is all. > > for this very small tests I highly recomend that you just open OllyDbg > and from it you open any .EXE (for example notepad.exe). > > Then, at the top pane (CPU code pane), just type an assembler > instruction, like add eax, 1. Hit enter, and OllyDbg will assemble > it for you. You'll see the corresponding bytes on that pane too. > > If you want to trace through the instructions, use F7, and watch > the registers change in the top right registers pane. > > any questions on this, let me know. > > OllyDbg is IMHO the easiest and fastest way of assembling on IA32. > Be aware that some instructions (many) may have more than a single > encoding, and your assembler ay differ from what OllyDbg (or any > other) does. You can test the other way around: generate bytes with > your assembler, input the bytes in OllyDbg, and see how it dissasembles > your instructions. > > richie > > _______________________________________________ > fonc mailing list > fonc@vpri.org > http://vpri.org/mailman/listinfo/fonc >
_______________________________________________ fonc mailing list fonc@vpri.org http://vpri.org/mailman/listinfo/fonc
