Timeline for Automatically convert x86 assembly to C
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 8, 2017 at 9:14 | answer | added | franck | timeline score: 0 | |
| Jun 20, 2014 at 7:57 | comment | added | Paul | You can use decompiler in IDA to produce a C file. It's not included in free version of IDA though. | |
| Jun 20, 2014 at 7:46 | history | tweeted | twitter.com/#!/StackReverseEng/status/479893047786737664 | ||
| Jun 20, 2014 at 1:46 | vote | accept | MxLDevs | ||
| Jun 20, 2014 at 1:46 | vote | accept | MxLDevs | ||
| Jun 20, 2014 at 1:46 | |||||
| Jun 19, 2014 at 21:40 | comment | added | MxLDevs | @perror I'm thinking more along the lines of subroutines and low-level structures. For example, after digging around with a debugger I've pinpointed the exact set of subroutines that perform a certain operation, and that is all that I need. Oh except there are a million instructions involved. | |
| Jun 19, 2014 at 21:40 | answer | added | Jason Geffner | timeline score: 12 | |
| Jun 19, 2014 at 21:32 | comment | added | perror | Decompilation is not that simple, the most complex thing is about rebuilding the high-level structures of the program that have been lost during the compilation process (variables, functions, modules/classes, ...). | |
| Jun 19, 2014 at 21:19 | comment | added | MxLDevs | An example I saw before is a simple XOR encryption algorithm that used a 64 KB key for some reason. That's not something you want to type out manually... | |
| Jun 19, 2014 at 21:16 | history | asked | MxLDevs | CC BY-SA 3.0 |