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
JADX has a nice line number mapping display where one can see the original line numbers in the decompiled source.
Would it be possible to add an option which actually updates the line number info present in the original DEX files with the new ones matching the decompiled source? I am aware that this invalidates APK signatures.
This feature would enable seamless source-code debugging.
I couldn't find anything that accomplished this, so added a feature to APKLab to write back to the smali files, and let APKLab orchestrate rebuilding the APK with the updated smali files: APKLab/APKLab#186
Initially explored modifying JADX to write back to the dex's directly, but found this challenging. Although JADX already keeps track of "sourcelines" from the dex, JADX primarily focuses on decompiling Dex files into Java source code. Implementing this functionality in JADX would involve considerable changes to the existing codebase, increasing the complexity and maintenance burden, and updating the dex binary debug_info_items statemachine seemed like a lot of work that smali/baksmali can already handle.
JADX has a nice line number mapping display where one can see the original line numbers in the decompiled source.
Would it be possible to add an option which actually updates the line number info present in the original DEX files with the new ones matching the decompiled source? I am aware that this invalidates APK signatures.
This feature would enable seamless source-code debugging.
Related to issue #476.
The text was updated successfully, but these errors were encountered: