Timeline for How to compile Hex-Rays decompiler generated code?
Current License: CC BY-SA 3.0
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 21, 2013 at 9:18 | comment | added | Willem Hengeveld | o, and what is wrong, is that '__thiscall' is apparently not defined for your compiler, you should '#define __thiscall' it to nothing to get rid of this specific error | |
May 21, 2013 at 9:16 | comment | added | Willem Hengeveld | it will not solve your problem, of a missing call type, but you should include "defs.h" ( found in the hexrays sdk ) in your file, it contains several macros used by hexrays. | |
May 7, 2013 at 13:01 | history | tweeted | twitter.com/#!/StackReverseEng/status/331755620510347264 | ||
Apr 30, 2013 at 19:36 | comment | added | Mellowcandle | @0xC0000022L I agree that the question lack vital information, However, I find this question related to the site. Decompiler are part of the RE process, and compiling the output is absolutly relevant to RE. | |
Apr 30, 2013 at 14:55 | history | edited | 0xC0000022L♦ | CC BY-SA 3.0 |
more spelling issues, trying to salvage this question
|
Apr 30, 2013 at 14:43 | history | edited | 0xC0000022L♦ | CC BY-SA 3.0 |
added 44 characters in body; edited title
|
Apr 30, 2013 at 14:30 | comment | added | 0xC0000022L♦ | Which compiler (and version) are you trying this in? Please edit your question. Also, this looks off-topic as it concerns forward engineering - and yes, I realize that the tool used is mainly used in RCE. | |
Apr 30, 2013 at 14:27 | review | Close votes | |||
Apr 30, 2013 at 15:59 | |||||
Apr 30, 2013 at 14:16 | history | edited | 0xC0000022L♦ | CC BY-SA 3.0 |
edited tags
|
Apr 30, 2013 at 13:29 | answer | added | Jason Geffner | timeline score: 6 | |
Apr 30, 2013 at 13:12 | history | edited | asheeshr | CC BY-SA 3.0 |
added 3 characters in body
|
Apr 30, 2013 at 13:07 | review | First posts | |||
Apr 30, 2013 at 18:28 | |||||
Apr 30, 2013 at 12:50 | history | asked | user1898 | CC BY-SA 3.0 |