Re: ASM => C
Unsolved Mysteries wrote:[color=blue]
> Anyone know of a translator that converts an Intel Pentium assembly
> listing into C? The quality of output code doesn't have to be great,
> so long as it's accurate.[/color]
I know there are decompilers that can generate C code, but the problem is
that it will just catch simple things, such as loops etc. The resulting C
source still is far from portable, especially because escapes to assembler
are made throughout the source.
One big issue is the stub that a C compiler puts in front of every program
it generates. This stub may not (and probably will not) be recognized as
such, causing the decompiler to generate some strange code which is
completely redundant.
If what you are trying to do is reverse engineer a program by getting the C
equivalent for it, any C generator will only help so little and
understanding of the machine on which the original program was intented to
run is still necessary, as well as some basic ASM knowledge.
If your goal is to generate a portable version of a piece of software, you
might as well forget about it and see if you can make a deal with the
original developer.
Good luck either way!
--
Martijn
Unsolved Mysteries wrote:[color=blue]
> Anyone know of a translator that converts an Intel Pentium assembly
> listing into C? The quality of output code doesn't have to be great,
> so long as it's accurate.[/color]
I know there are decompilers that can generate C code, but the problem is
that it will just catch simple things, such as loops etc. The resulting C
source still is far from portable, especially because escapes to assembler
are made throughout the source.
One big issue is the stub that a C compiler puts in front of every program
it generates. This stub may not (and probably will not) be recognized as
such, causing the decompiler to generate some strange code which is
completely redundant.
If what you are trying to do is reverse engineer a program by getting the C
equivalent for it, any C generator will only help so little and
understanding of the machine on which the original program was intented to
run is still necessary, as well as some basic ASM knowledge.
If your goal is to generate a portable version of a piece of software, you
might as well forget about it and see if you can make a deal with the
original developer.
Good luck either way!
--
Martijn
Comment