Code obfuscation and debugging

Question

I am creating a SDK and obfuscating the code through proguard/dexguard but I am not sure how my developers can debug the code if the code is obfuscated. Not obfuscating the SDK code is not an option.

Code obfuscation and debugging don't seem to work parallely unless I am missing something here.

Dario Incalza · Accepted Answer · 2016-02-03 16:22:17Z

1

You can ask DexGuard to print a mapping file. This is achieved by including the option -printmapping "mapping.txt" in the DexGuard configuration file. Together with this mapping and a stacktrace you can use the retrace.jar tool, included with DexGuard, to de-obfuscate the stacktrace and debug the SDK.

All the information on how to do this can be found in the docs/ directory shipped with DexGuard.

Cheers,

Dario

answered Feb 3, 2016 at 16:22

Dario Incalza

655 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Anil Gorthy Over a year ago

Actually, I was looking for suggestions on how the developers that use my SDK will debug their apps that are built using my SDK. If they want to step through the code, they will be looking at obfuscated code - of course some of the public interfaces are not obfuscated. What you suggested works for me as the guy who built the SDK to de-obfuscate the code using the mapping.txt.

Dario Incalza Over a year ago

Unless you're willing to share the mapping file, nobody can debug using unobfuscated code. DexGuard removes all debugging information (sourcefile names and linenumbers etc)

Collectives™ on Stack Overflow

Code obfuscation and debugging

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related