Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

Category:Static Analysis

From Wiki
Jump to: navigation, search

So what is it? Static analysis means the study of things that are not changing. However, in software terms, this definition can be refined as the study of source or binary code that is not currently running. You already know that you need a debugger or profiler to analyze running code, but you can learn a lot from code without ever running a program.

You can ensure that the source code is free from critical defects and adheres to following the Symbian API conventions. You can also detect common performance problems, such as Resource leaks, high stack use, and infinite loops. You can even examine the imports of each class to understand what other classes it depends on or which classes depend on it. None of this requires the program to run or even to compile.

Static Analysis- BEST Practices- Symbian OS and Coverity

Overview: Automated Defect Detection in Symbian OS Environments with Coverity Static Analysis

Philippe Gabriel, Chief Technology Architect, Symbian Ben Chelf, CTO, Coverity

"For us to ensure stability of mobile applications, we must be able to find and fix critical code defects with accuracy and efficiency."

This category currently contains no pages or media.

This page was last modified on 7 December 2008, at 19:50.
60 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.


Thank you!

We appreciate your feedback.