Contents fo executable files

smeezekitty · 03-29-2015, 04:08 PM

Quote:

Originally Posted by jpollard

Again, WHY.

You can GET the source to the utilities if you want.

Well it is worth noting that compilation isn't completely irreversible. But decompilation is hit or miss (mostly miss)

jpollard · 03-29-2015, 05:05 PM

It definitely is not completely reversable.

What gets lost is where compile options (combined with configuration options) can and will eliminate entire code sections. The result of decompilation in no way comes close to the original.

Part of what gets lost is the portability that the original had. What is "decompiled" is focused on one and only one platform.

smeezekitty · 03-29-2015, 06:04 PM

Quote:

Originally Posted by jpollard

It definitely is not completely reversable.

What gets lost is where compile options (combined with configuration options) can and will eliminate entire code sections. The result of decompilation in no way comes close to the original.

Part of what gets lost is the portability that the original had. What is "decompiled" is focused on one and only one platform.

Not to mention symbol names are usually lost. You end up with variable names like integer_01 integer_02 and similar function names.

jpollard · 03-30-2015, 05:57 AM

Quote:

Originally Posted by smeezekitty

Not to mention symbol names are usually lost. You end up with variable names like integer_01 integer_02 and similar function names.

yes, and not just usually - all local variable names disappear, and if the executable is stripped so too are the global names, leaving only those for binding with shared libraries. Structure reconfigurations done by the compiler for the platform as well (mostly the padding added).

rtmistler · 03-30-2015, 06:02 AM

Wasting our time, OP hasn't returned with any responses.