r2dec-js
r2dec-js copied to clipboard
wargio
[WASM] Remove wasm from r2dec and make it as a standalone plugin
Since WASM is particular, it would be better if we remove it from r2dec and make it as a standalone plugin.
WASM is like ESIL, a stack based language which requires some magic analysis which r2dec cannot do.
Current issues:
- WASM flows guards are complex without emulation
- Requires many interactions with r2 itself to get the call names/symbols
if anybody wants to help https://github.com/wargio/r2dec-wasm
On 30 Nov 2018, at 11:12, Giovanni [email protected] wrote:
Since WASM is particular, it would be better if we remove it from r2dec and make it as a standalone plugin.
R2dec plugin?
WASM is like ESIL, a stack based language which requires some magic analysis which r2dec cannot do.
Current issues:
WASM flows guards are complex without emulation
Whats that
Requires many interactions with r2 itself to get the call names/symbols
Why?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
because wasm is not easy, so i prefer to have a better decompilation via a separate r2 plugin
R2 plugin why? Doesnt makes more sense to put yhis in r2dec?
On 30 Nov 2018, at 12:10, Giovanni [email protected] wrote:
because wasm is not easy, so i prefer to have a better decompilation via a separate r2 plugin
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Why not just keep this abstraction in r2dec instead of forking it?
On 30 Nov 2018, at 13:24, Giovanni [email protected] wrote:
no. the code structure i want to use is different
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
because i don't know where to place it. it requires a different cycle of analysis. i'll think about it..