在混淆器手册问题解决方案部分，介绍了代码在混淆过程中你可能碰到的其他常见问题。
The Troubleshooting section of the ProGuard Manual Outlines other common problems you might encounter when your code gets stripped away.
但是，对于混淆器来说，大多数情况做出正确的分析是困难的，并且它或许会删除在它看来是无用的，但对于程序来说却确实需要的代码。
However, many situations are hard for ProGuard to analyze correctly and it might remove code that it thinks is not used, but your application actually needs. Some examples include.
因为Ruby源代码已经编译成了原生机器码（正如我们使用JIT编译器在运行时所做的一般），因此这也是混淆代码的一个不错的方式。
The Ruby source code is compiled into native machine code (same process as we do at runtime with the JIT compiler), so it's also a good way to obfuscate the source code.
攻击CFG生成进程也可以是通过混淆汇编代码以致它不能够正确地确定跳转指令的目标，比如使用寄存器指示跳转目标。
The CFG generation process can also be attacked by obfuscating the assembly code such that one cannot determine the correct target of a jump instruction, such as using a jump through register.
攻击CFG生成进程也可以是通过混淆汇编代码以致它不能够正确地确定跳转指令的目标，比如使用寄存器指示跳转目标。
The CFG generation process can also be attacked by obfuscating the assembly code such that one cannot determine the correct target of a jump instruction, such as using a jump through register.
应用推荐