godzil/dcc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Readme.md

Browse Source
This commit is contained in:
Artur K. 2014-06-05 15:01:12 +02:00
parent 337a6c44aa
commit d8c66e7791
1 changed files with 12 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
Readme.md
View File

@ -1,3 +1,5 @@
I've fixed many issues in this codebase, among other things - memory reallocation during decompilation.
To reflect those fixes, I've edited the original readme a bit.
----------------------------- -----------------------------
Original readme: Original readme:
@ -81,10 +83,11 @@ are:
- the large memory model problem & scanf() - the large memory model problem & scanf()
- dcc's error message shows a p option available which doesn't - dcc's error message shows a p option available which doesn't
exist, and doesn't show an i option which exists. exist, and doesn't show an i option which exists.
- there is a nasty problem whereby some arrays can get reallocated to
<del>- there is a nasty problem whereby some arrays can get reallocated to
a new address, and some pointers can become invalid. This mainly a new address, and some pointers can become invalid. This mainly
tends to happen to larger executable files. A major rewrite will tends to happen to larger executable files. A major rewrite will
probably be required to fix this. probably be required to fix this.</del>
For more information refer to the thesis "Reverse Compilation For more information refer to the thesis "Reverse Compilation
Techniques" by Cristina Cifuentes, Queensland University of Techniques" by Cristina Cifuentes, Queensland University of
@ -99,13 +102,13 @@ Using dcc
Here is a very brief summary of switches for dcc: Here is a very brief summary of switches for dcc:
a1, a2: assembler output, before and after re-ordering of input code * a1, a2: assembler output, before and after re-ordering of input code
c: Attempt to follow control through indirect call instructions * c: Attempt to follow control through indirect call instructions
i: Enter interactive disassembler * i: Enter interactive disassembler
m: Memory map * m: Memory map
s: Statistics summary * s: Statistics summary
v, V: verbose (and Very verbose) * v, V: verbose (and Very verbose)
o filename: Use filename as assembler output file * o filename: Use filename as assembler output file
If dcc encounters illegal instructions, it will attempt to enter the so called If dcc encounters illegal instructions, it will attempt to enter the so called
interactive disassembler. The idea of this was to allow commands to fix the interactive disassembler. The idea of this was to allow commands to fix the