We think you will agree that that the extra time needed to achieve this high level of accuracy is justly compensated for by the time saved when hand correcting the output. Although the customized modeling performed by the disassembler does increase processing time, the result is a dramatic reduction of incorrect opcode translations. This output can be manually edited or saved to disk for future reference.
#Delphi Exe Decompiler code
The decoding process concludes by generating labels for any items that remain unidentified and setting the output positions for all of the various items found in the target file.Īfter all processing has been completed, the disassembler displays the resulting source code for the target file. If the repeated scanning option is selected, this step is repeated until the disassembler has resolved any outstanding references. Information accumulated in the Jumps list is evaluated first, followed by the information in the Rets list, until both lists are empty. When the primary branch of the decoding process finishes executing, the remaining information from the Jumps list and the Rets list is processed. As the information from the Jumps list and the Rets list accumulates, the decoding process begins to emulate the execution of the code found within the target file. These addresses are then arranged according to the degree of certainty regarding their identification. The Jumps list stores the addresses to positively identified instructions and the Rets list stores the addresses to tentatively identified instructions. In turn, this information is used to form the Jumps list and the Rets list. If a relocation table is found, the information is used to detect the absolute offsets to the various content items in the file for example: mov eax, offset LF46A, jmp LA49FE. The disassembler will decompile files built with other compilers too.Īfter the compiler has been identified, the disassembler searches the target file for a relocation table. Moreover, given this information, identifying most of the objects, procedures, variables, types etc. Forehand knowledge of how a compiler puts files together improves the guesswork involved in determining the data allocation patterns within the target file. The disassembly process begins by identifying the compiler used to build the target file. At Heaventools, improving the disassembler is an ongoing part of our PE Explorer development efforts. The Borland VCL object model is designed in such a way that we think it will be possible to reproduce the original assembly language source code perfectly. In order to meet this challenge, we developed a customized model, specifically designed to reduce incorrect data type identifications. Separating code from data can be extremely difficult, especially when the initial code includes countermeasures intended to hinder disassembly. The fundamental challenge in disassembling compiled files is to correctly interpret the examined data. To facilitate additional hand coding, however, the disassembler utilizes a qualitative algorithm designed to reconstruct the assembly language source code of target binary win32 PE files EXE, DLL, OCX with the highest degree of accuracy possible.
#Delphi Exe Decompiler manual
The PE Explorer disassembler assumes that some manual editing of the reproduced code will be needed. While as powerful as the more expensive, dedicated disassemblers, PE Explorer focuses on ease of use, clarity and navigation. To that end, some of the functionality found in other products has been left out in order to keep the process simplefast and easy to use. The PE Explorer win32 disassembler is designed to be easy to use compared with other disassemblers.