Mostly, software development projects depend on code test, structural test and performance test to identify bugs.
大部分软件开发项目依靠结合代码检查、结构测试和功能测试来识别软件缺陷。
We instituted peer reviews to help identify bugs before they hit production, and we observed something very interesting: few bugs were being identified during the reviews.
我们建立了同级评审来帮助我们在应用系统的bug影响生产环境的系统之前识别出他们，并且我们观察到一些事情非常有趣：在评审过程中很少的bug被识别出来。
As a rule, code compiled with full optimization can be difficult or impossible to debug, making it very difficult to identify bugs that may be causing the system to function incorrectly.
通常，经过完全优化的编译代码很难或者几乎不可能进行调试，这就加大了发现那些造成系统功能错误所在的难度。
More specifically, static analysis is able to look for coding generally concerned with coding style to identify rudimentary bugs.
更特别的是，静态分析能够寻找与编码形式相关的编码，以识别基本的代码漏洞。
It's much cheaper to identify testing gaps, fill them, and find the bugs before release.
在发布版本之前识别测试漏洞，填充并找到这些错误，成本会低得多。
Of course, not all bugs occur on all paths, and due to our path analysis, we're able to identify just the paths that contain defects without a lot of noise.
当然，并非所有路径上都会出现Bug的，通过我们的路径分析，我们可以识别包含缺陷的调用路径，并且不会太多噪音干扰。
Bug patterns identify problematic coding practices that are frequently found in the neighborhoods where bugs live.
bug模式会标识有问题的编码实践，它们常常位于bug所在的区域。
To help us identify new bugs and minimize duplicate reports, please read the known issues, useful tips and have a look on the discussion forum to see if others have reported similar issues.
为了帮助我们寻找新的漏洞，减少重复的报告，请阅读已知问题、实用技巧以及访问论坛查看是否有其他人报道类似的问题。
To help us identify new bugs and minimize duplicate reports, please read the known issues, useful tips and have a look on the discussion forum to see if others have reported similar issues.
为了帮助我们寻找新的漏洞，减少重复的报告，请阅读已知问题、实用技巧以及访问论坛查看是否有其他人报道类似的问题。
应用推荐