Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I find myself needing more detail in my reported stack traces, but I’m concerned that by including the extra data (by using -keepattributes SourceFile,LineNumberTable) I’m making my app even easier to reverse engineer. Is this the case, and if so, by how much?
ProGuard manual > Examples > Producing useful obfuscated stack traces
The SourceFile attribute is required, because Oracle/Sun’s Java virtual machine otherwise does not include line numbers in stack traces, which is what you really want (and which is quite harmless on its own). I haven’t checked if this is true for Android’s Dalvik virtual machine.
As for a solution, ProGuard can keep the SourceFile attribute but replace its contents by a meaningless string of your choice, e.g.
The value of the string is not important for interpreting the stack traces. Picking a string like “SourceFile” avoids increasing the class file sizes, because this string is already present by definition.