You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when decompiling function main of fmt.zip the decompilation process crashes due to an invalid condition.
More precisely, the reaching condition of an AST node is evaluated as false because the type of a constant is wrong. (The problem with type propagation is tracked in Issue #42.)
Nevertheless, the program should not crash. The program occurs because the function _condition_string does not assume that a condition is true or false.
Proposal
There are multiple options for this problem.
In general, if a condition is false, then we can simply remove the true branch and execute always the false branch, i.e., we can substitute the condition node with the false branch. Symmetrically, one would replace each condition node with condition true by its true branch. But, in cases like this where the condition should not be false, we may lose content we do not want to lose.
We simply have a condition that is false or true and add this scenario to the function _condition_string.
What happened?
Currently, when decompiling function main of fmt.zip the decompilation process crashes due to an invalid condition.
More precisely, the reaching condition of an AST node is evaluated as false because the type of a constant is wrong. (The problem with type propagation is tracked in Issue #42.)
Nevertheless, the program should not crash. The program occurs because the function
_condition_string
does not assume that a condition is true or false.Proposal
There are multiple options for this problem.
_condition_string
.In both cases, a warning could be nice.
How to reproduce?
Try to decompile main in fmt.zip
Affected Binary Ninja Version(s)
2.4.2846
The text was updated successfully, but these errors were encountered: