Re: Creating a dis-assembler on my own - shucks !
From: R.Wieser (rwieser-killthis-_at_xs4all.nl)
Date: 01/18/04
- Next message: Matt Taylor: "Re: Linker error"
- Previous message: Bx. C: "Re: Linker error"
- In reply to: Dr John Stockton: "Re: Creating a dis-assembler on my own - shucks !"
- Next in thread: Gerhard W. Gruber: "Re: Creating a dis-assembler on my own - shucks !"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 18 Jan 2004 21:00:19 +0000 (UTC)
Dr John Stockton <spam@merlyn.demon.co.uk> schreef in berichtnieuws
aikaUXIzvpCAFwai@merlyn.demon.co.uk...
> JRS: In article <4009aefa$0$143$e4fe514c@dreader5.news.xs4all.nl>, seen
Hello John,
> in news:comp.lang.asm.x86, R.Wieser <rwieser-killthis-@xs4all.nl> posted
> at Sat, 17 Jan 2004 22:01:05 :-
> >
> >I allready decided that whenever my disassembler encounters a command
(one
> >or more bytes) that it does not recognise, it will only output the first
> >byte. :-) That way it will maybe be able to get into sync at the next
> >byte.
>
> ISTM that an intelligent disassembler should start at the execution
> origin, and proceed straight down the code until an unconditional
> branch; it should then go to the destination of that branch, and
> continue, etc. It should stop on finding a return-to-OS, or code
> already disassembled.
Let's start with a "dumb" disassembler first, as that poses enough problems
as it is. Not the coding, but finding the commands and their permitted
arguments ...
After that I will probably write a wrapper-routine that will do just as you
said, and I allready done before to a C64 disassembler I once wrote :-)
But first the disassembler please ...
Regards,
Rudy Wieser
- Next message: Matt Taylor: "Re: Linker error"
- Previous message: Bx. C: "Re: Linker error"
- In reply to: Dr John Stockton: "Re: Creating a dis-assembler on my own - shucks !"
- Next in thread: Gerhard W. Gruber: "Re: Creating a dis-assembler on my own - shucks !"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|