What are the different ways to get the instrumentation data of Testwell CTC++?
There are different ways how you can use Testwell CTC++ to measure code coverage on your embedded target.
One approach is to use our HOTA (Host-Target) Workflow where you can customize the provided runtime implementation according to the capabilities of your target.
The Host-Target Add-On called HOTA provides coverage measurement with Testwell CTC++ for (embedded) targets.
With HOTA, the following use case is supported:
The source code is instrumented and compiled at the host using a cross-compiler for the target.
The instrumented program is executed on the target.
Execution counters have to be brought back to the host.
The generation of coverage reports typically takes place at the host.
A target in this sense can be an embedded target or any system with a different operating system.
Also kernel mode applications, like drivers, can be instrumented using HOTA.
Essentially the HOTA package consists of a couple of well-commented C source files building the Testwell CTC++ run time.
The files are "vanilla C" and compile with any decent C compiler.
Another approach is to use the Bitcov Workflow which keeps the counter data within application memory that will be dumped at any time using appropriate means.
Which way would be best in your setup can be elaborated during a free evaluation of Testwell CTC++.