Search Results for "c call tree"

Most test frameworks for C require a lot of boilerplate code to set up tests and test suites -- you need to create a main, then register new test suites, then register the tests within these suites, and finally call the right functions. This gives the user great control, at the unfortunate cost of simplicity. Criterion follows the KISS principle, while keeping the control the user would have with other frameworks.

...The flexible approach enables the inclusion of many types of tests, such as memory leak checks (using valgrind), coding rule checks, complexity checks, etc. Tests are run by a simple call to hwut in a base directory of a project. In particular for C, HWUT supports make file generation using 'sos' and 'sols' modes. Remote control-able function stubs may be generated using the 'stub' mode. Test cases can be generated using the 'gen' mode, and state machine walkers by the 'sm_walker' mode. Over the last decade HWUT has matured towards a full fledged unit test tool for a wide variety of applications.

KCachegrind visualizes traces generated by profiling, including a tree map and a call graph visualization of the calls happening. It's designed to be fast for very large programs like KDE applications.

First ever security assessment tool developed for Microsoft Office Communication Server R1/R2. OAT is designed to check security posture of MS OCS deployments.