??? 07/14/07 14:47 Read: times |
#141876 - Controlling the disassembly Responding to: ???'s previous message |
Russell Bull said:
"How can a disassembler decide the logical end of code."
It can't! Well, not easily. What happens if there are many blocks of code separated by ffh? What constitutes the logical end of code? Unless your disassembler goes through a keeps a track of all jumps and calls, it has no idea of where the code starts and ends. How do you know where the code starts and ends? The -t option does a code analysis, which among other things, does keep track of jumps and calls. Alternatively, you can create a control file (same name as file being disassembled, but with .ctl extension). The control file can tell d52 many things about the code including where it ends. (Note that use of -t will create a new ctl file, overwriting any existing file of the same name.) Also, d52 will assume that long blocks of 0x00 or 0xff are not valid and will not do a disassembly of them, unless you force it to with a -c, -d or similar directive in a control file. See the documentation for complete info. |
Topic | Author | Date |
D52 binaries | 01/01/70 00:00 | |
end of code | 01/01/70 00:00 | |
Same question! | 01/01/70 00:00 | |
Controlling the disassembly![]() | 01/01/70 00:00 |