Tracing is a specialized use of logging to record information about a program’s execution. It is typically used by programmers for debugging purposes. A trace captures every single instance at which an instrumentation point is executed during operation. For example, if you’re using RapiTime, you need need to use a trace. Each time an instrumentation point is executed, a trace entry is generated containing the instrumentation point ID and a timestamp. The length of the trace depends upon the number of instrumentation points in your code and also on the length of the tests. The trace data can be stored on the target if there’s enough free memory, or output to an external capture device, for example an RTBx. A map captures whether an instrumentation point is executed or not. For instance, if you’re using RapiCover, you can use a map, which stores coverage data in a fixed-size area of memory. The size of the map depends on the number of instrumentation points in your code, not on the length or number of tests.