Trace discontinuities

If part of the trace is missing, it is because one of the following situations exists:

• Tracing was stopped at one point and restarted at a later point.
• One processor fills its trace buffer and stops tracing, while other processors continue tracing.
• Event records in the trace buffer were overwritten before they could be copied into the trace log file.

In any of the above cases, the splat command will not be able to correctly analyze all the events across the trace interval. The policy of splat is to finish its analysis at the first point of discontinuity in the trace, issue a warning message, and generate its report. In the first two cases, the message is as follows:

     TRACE OFF record read at 0.567201 seconds. One or more of the CPUs has
     stopped tracing. You might want to generate a longer trace using larger
     buffers and re-run splat.

In the third case, the message is as follows:

     TRACEBUFFER WRAPAROUND record read at 0.567201 seconds. The input trace
     has some records missing; splat finishes analyzing at this point. You
     might want to re-generate the trace using larger buffers and re-run splat.