: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means waiting times in the issue tracker are very long and mostly depend on community. Sorry for the inconvenience.
State: closed 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.
At the moment I see that FFDec stores error log in:
and I see that every time you open .swf file the log file is being re-written (clearing
anything that was inside of it before).
My suggestion is to store logs in:
+ have a separate log file every time you open a swf file.
Also, instead of just storing errors store also the whole process, file information and
Example of how the log file could look:
FFDec Version: 1.7.0
OS: Windows 7 Ultimate (64-bit)
File location: C:\test\myfile.swf
00:29:59.345 > Loading file...
00:30:01.184 > Decompiling (this, that, this)....
00:30:02.952 > Decompiling (this, that, this)...
00:30:02.952 > Decompilation done
00:30:03.005 > File loaded
00:30:03.931 > Creating window...
00:30:04.191 > Window created
Loaded in 159 seconds
== File information ==
Size: 150 KB
Flash Version: 9
This way I think you could request people to provide the log file when they create issues
and it would help understand better what is going on and you wouldn't have to ask people
information about their system etc.