Search Results for "gcov"

The AWS SigV4 Library is a standalone library for generating authorization headers and signatures according to the specifications of the Signature Version 4 signing process. Authorization headers are required for authentication when sending HTTP requests to AWS. This library can optionally be used by applications sending direct HTTP requests to AWS services requiring SigV4 authentication. This library has no dependencies on any additional libraries other than the standard C library. This...

The Fleet Provisioning library enables you to provision IoT devices without device certificates using the Fleet Provisioning feature of AWS IoT Core. For an overview of provisioning options available, see Device provisioning. This library has no dependencies on any additional libraries other than the standard C library, and therefore, can be used with any MQTT library. This library is distributed under the MIT Open Source License. This library has gone through code quality checks including...

The AWS IoT Device Shadow library enables you to store and retrieve the current state (the “shadow”) of every registered device. The device’s shadow is a persistent, virtual representation of your device that you can interact with from AWS IoT Core even if the device is offline. The device state is captured as its “shadow” within a JSON document. The device can send commands over MQTT to get, update and delete its latest state as well as receive notifications over MQTT about changes in its...

The Device Defender library enables you to send device metrics to the AWS IoT Device Defender Service. This library also supports custom metrics, a feature that helps you monitor operational health metrics that are unique to your fleet or use case. For example, you can define a new metric to monitor the memory usage or CPU usage on your devices. This library has no dependencies on any additional libraries other than the standard C library, and therefore, can be used with any MQTT client...

Automation of Unit and System Tests. Tests can be implemented in any language and on many platforms. 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....

ggcov is a GTK+ GUI for exploring test coverage data produced by C programs compiled with gcc --coverage. It's basically a GUI replacement for the gcov program that comes with gcc.

bcov is a code coverage tool similar to gcov. Unlike gcov, it does not require recompiling the project for coverage. Coverage is determined by using temporary breakpoints, which causes minimal overhead. gcov produces a lcov style coverge report.

It's a integrated performance analysis tool with GUI, which is integrated with various utilities such as strace, Gcov, Gprof, proc etc which are open released and are for analyzing performance of linux system

STUBborn C is a tool that allows you to create a module test framework for SW modules developed in C. The framework includes: Stubs needed to link the module; A sample Makefile to build, run tests and check code coverage; Test templates using CUnit.

bepro graphically visualizes profilingdata from external profilingtools (gcov, gprof,...) mapping the given values to colors. It gives you a quick overview onto your code from a "birds-eye-view". bepro is similar to "Tarantula".

The Ultimate Test Tool Infrastructure. This is a framework for commercial as well as non-commercial test tools. It allows to combine tools by supporting Purify, Insure++, QAC/QAC++, gcov, cppunit to build a unit testsuite.

gcov-eclipse is an Eclipse plug-in that will extend CDT to provide code-coverage testing to C/C++ projects by using the gcov program. It will integrate into the CDT's launch and managed build system.