Moreover, Visual Basic 5 executable files are a mix of Subroutine code and Form data. EXE file was compiled without debugging information, if a program data base file (.PDB) or Codeview (C7) format was used, or if the optimization option of the compiler was enabled, the output produced will not be very good. REC will try to use whatever information is present in the. Will need to improve it to support in-program definition of types and function parameters.Īlthough REC can read Win32 executable (aka PE) files produced by Visual C++ or Visual Basic 5, there are limitations on the output produced. Interactivity is supported, limited to definition of sections, labels and function entry points.Some standard Posix and Windows APIs are already provided in the Rec Studio package. Types and function prototype definitions can be specified in text files.However, C++ is a very broad and difficult language, so some features like templates won’t likely be ever supported. C++ is partially recognized: mangled names generated by gcc are demangled, as well as inheritance described in dwarf2 is honored.Symbolic information support using Dwarf 2 and partial recognition of Microsoft’s PDB format.Multihost: Rec Studio runs on Windows XP/Vista/7, Ubuntu Linux, Mac OS X.It uses more powerful analysis techniques such as partial Single Static Assignment (SSA), allows loading Mac OS X files and supports 32 and 64 bit binaries.Īlthough still under development, it has reached a stage that makes it more useful than the old Rec Studio 2. REC Studio 4 is a complete rewrite of the original REC decompiler. It has been designed to read files produced for many different targets, and it has been compiled on several host systems. It reads a Windows, Linux, Mac OS X or raw executable file, and attempts to produce a C-like representation of the code and data used to build the executable file.
0 kommentar(er)
