+ 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.
> What steps will reproduce the problem?
Decompile an swf and try to edit a script to use an existing constant string. (Either
pcode or actionscript)
> What is the expected output? What do you see instead?
Instead of it reusing the existing constant from the decompiled swf, it creates a new one.
(Subsequent edits will use the newly created constant, not create more)
This is a problem when the original constant and the newly created clone have indexes with
a different number of bytes because the pcode will always use the newly created constant
in edits, you have to edit the raw hex manually to use the original constant, which will
mis-align the offsets.
> What version of the product are you using? Is it "nightly build"? Which operating system
do you have?
> Please provide any additional information below. If the problem is related to a SWF
file, attach it here, otherwise we can't help you.