: 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: 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 some code
- Attach decompiled code to a debugger
- Try to follow the code but debugger takes you to a correct n incorrect line
> What is the expected output? What do you see instead?
On debugging jump correctly to decompiled code
Debug take me to correct file but to an incorrect line, making debug a pain.
> What version of the product are you using? On what operating system?
JPEXS 5.3.0 on Windows 7. Debug with eclipse indigo.
> 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 don't know if flex provide debug information (so you can jump to correct line on debug)
If you can point me where decompilation writes output files and where to find line
position for compiled code I can provide a patch from github.
Maybe we can do reverse thing - we can decompile the file and then modify the original SWF
file to contain match line numbers from decompiled scripts. I already discissed it with
somebody earlier. To make the SWF file debuggable with esctracted scripts...
Would you like this feature?
I'm not talking about 100% precision.
These came from a decompiled code
debug 1 "VAR_1" 5 43
that debug line is line info, isn't it?
Other decompilers try (not perfectly) to respect that info to output a debuggeable file.
That is what I'm looking for: Where to read that information to try to respect that debug
info. Please lead me to codebase to propose a patch
That approach is scary. I had already thought. Since I have the decompiled code I can
compile it again. But that way you cannot trust your debug.
Since debug works (if you locate where on file you are really) Try to create a file that
respect the debug info seems better approach.
Anyway (since you have an experimental option to edit code) I think both approach would be
nice, just let people choice what to use.
A first test changing manually decompiled code to respect that debugline info works
> I forgot to add this line to prior example
Any clues about where decompiled code is output and how to read debug info?
The decompiler already loads the linenumbers from this instruction.
The only thing to do here is format the code the way it matches the linenumber info.
This is not an easy task. Each GraphTargetItem has getLine() method which returns the line
taken from debugInfo. This can be helpful...