Changes between Version 32 and Version 33 of TBR/UserManual/RTEMS_Coverage_Analysis


Ignore:
Timestamp:
Sep 9, 2009, 10:03:06 PM (10 years ago)
Author:
JoelSherrill
Comment:

/* How it was Done */ Add information on Coverage Reader/Writer? classes

Legend:

Unmodified
Added
Removed
Modified
  • TBR/UserManual/RTEMS_Coverage_Analysis

    v32 v33  
    2626
    2727The RTEMS Code Coverage Analysis process was designed to be as automated as possible.  The coverage testing is performed using a processor simulator in conjunction with a set of RTEMS specific support scripts.  The code to be analyzed is linked together as a single relocatable with special start (''start_coverage'') and end (''end_coverage'') symbols.  The relocatable is then linked to the same address in every test from the test suite.  Each test is then executed on a processor simulator that gathers information about which instructions were executed and produces a coverage map for the test.  After all tests have finished, the support script ''covmerge'' is used to merge all coverage maps into a unified coverage map for the entire test suite and to produce reports that identify the uncovered code.  The picture shown provides the general flow of the process.
     28
     29Each source of coverage maps (e.g. simulator, hardware debugger, etc.) may produce a coverage map in a different format.  The covmerge tool is implemented using C++ classes and provides for inheriting new Coverage Reader and Writer classes for specific coverage map formats.  It currently supports the formats produced by the TSIM and Skyeye simulators.
    2830
    2931<br style="clear: both" />