Proguard Instrumentation Output

I'm experimenting with proguard now, which is easier to use from inside an eclipse. I exported a signed version of my application using a deliberate error that crashes for testing. After I get the stack to trace and run retrace -verbose mapping.txt stack.txt, instead of giving me where the error occurs, it gives me a class where the error occurs and lists one of the methods, one of which is a method in which an exception.

I used the official guide for all this and edited the logcat stack trace capture in the same format as the dev console. Does anyone know what the problem is?

+8
android eclipse obfuscation proguard
source share
1 answer

If your obfuscated code does not contain information about the line number, matching the name of the running method (for example, 'a') with the name of the original method can no longer be unambiguously possible due to name overloading. The examples in the ReTrace manual illustrate the difference.

To avoid this effect, you can save line number information during the obfuscation phase, as shown in the example in the ProGuard manual .

+14
source share

Source: https://habr.com/ru/post/650774/


All Articles