+ 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: 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.
> What steps will reproduce the problem?
In a bash script, build an array of parameters to pass to ffdec.sh. Then launch ffdec.sh
> What is the expected output? What do you see instead?
The parameters are split up like this:
instead of like this:
13.:/home/kev/word-realms-mods/mods/Original in Italian/Word.PFR.2017.pcode
...and even if you add extra quotes around such paths, you get things like this:
13.:"/home/kev/word-realms-mods/mods/Original in Italian/Word.PFR.2017.pcode"
or like this:
13.:'/home/kev/word-realms-mods/mods/Original in Italian/Word.PFR.2017.pcode'
...which inevitably cause ffdec to fail with "I/O error during reading".
> What version of the product are you using? On what operating system?
Latest nightly on Mint 16.
> Please provide any additional information below. Attach the file you have problem with
if neccessary. If you do not want to publish files YOU CAN CHANGE VISIBILITY TO PRIVATE
I'm not sure how I had done this before and not had a problem...perhaps I had replaced the
nightly and then happened to not test with a space-filled path.
Anyway, it's easy to fix, just change the very first line of ffdec.sh from:
Thanks for including this fix in the latest nightlies; however, the file got saved with
Windows line endings, so trying to launch in Linux gives the error:
^M: bad interpreter: No such file or directory