+ update 2020: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means we will NOT develop new features and/or fix most of bugs. We left the tracker running in case somebody from community would like to work on it. Sorry for the inconvenience.
State: new new: Initial state. As long as issue is in this state, the work on the issue has not yet begun. opened: Opened state means developer started working on the issue. Feature/Fix will probably be in the next release. postponed: This means developer is not working on it now, for some reason it cannot be implemented now. Issue may be opened again in the future. upgraded: Issue is in upgraded state when developer made changes to the program and new version was released. closed: This means the user is satisfied with issue results and no more changes are needed. invalid: These issues cannot be solved. ignored: Developer decided to take no action on this issue. returned: Program changes were made but user is not satisfied and returned the issue.
Is there a documentation/roadmap for the decompiler? If not, how do I get started with
understanding the code?
Yes, there is no documentation. We rather invest our expensive time to implement new
features or fix bugs, sorry :-(.
There are few JavaDoc comments in the code. Some function/class names are less intuitive,
There are only two of us who actually write most of the code, we have also regular jobs
during week so that's why.
For user documentation, there are few sections on our webpage (See Features in menu)
Is there any paper or book that helped inspire the main decompilation architecture and
techniques of the code (converting to control-flow-graph, then translating to GraphTarget
representation, ...)? There seem to be quite some interesting concepts behind the code.