Defect in XSH Tracing

[yyyyyyyy@xxxxxxxxxx]

        Defect report from : William Toth , IBM Austin

(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)

@ page 630 line 3228 section Tracing objection {WLT-VSTRC-4}

Problem:

Edition of Specification (Year): 2004

Defect code :  1. Error

The SUSv3 Tracing section specifies this for POSIX_TRACE_RESUME

The POSIX_TRACE_RESUME trace event shall be reported with a timestamp equal to 
the timestamp of the first valid trace event reported after the overflow 
condition ends and shall be reported before this first valid trace event. This 
is an indication that the trace system is reliably recording trace events after 
an overflow condition.


Because of the unknown period of time that could occur between the 
POSIX_TRACE_RESUME event and the next valid trace event we don't think setting 
the POSIX_TRACE_RESUME event timestamp to that of the next event's timestamp is 
correct.

We believe a better requirement would be to set the timestamp of the 
POSIX_TRACE_RESUME event to when it occurs. That way when a log is cleared 
because of an overflow condition, a clear indication of when the log was 
cleared will be recorded.

It seems strange to require the controller to have to check the previous event 
and see if it is a POSIX_TRACE_RESUME event and then go back and modify it's 
timestamp.

Action:

Change the requirement as described above.