-Common Trace Format (CTF) Specification (v1.7)
+Common Trace Format (CTF) Specification (pre-v1.8)
Mathieu Desnoyers, EfficiOS Inc.
the network, is expected to be either on permanent or temporary storage in a
virtual file system. Because each event stream is appended to while a trace is
being recorded, each is associated with a separate file for output. Therefore,
-a stored trace can be represented as a directory containing one file per stream.
+a stored trace can be represented as a directory containing zero, one or
+more files per stream.
Meta-data description associated with the trace contains information on
trace event types expressed in the Trace Stream Description Language
Event packet context (all fields are optional, specified by TSDL meta-data):
-- Event packet content size (in bytes).
-- Event packet size (in bytes, includes padding).
+- Event packet content size (in bits).
+- Event packet size (in bits, includes padding).
- Event packet content checksum. Checksum excludes the event packet
header.
- Per-stream event packet sequence count (to deal with UDP packet loss). The
event header as selector.
The target dynamic scope must be specified explicitly when referring to
-a field outside of the local static scope. The dynamic scope prefixes
-are thus:
+a field outside of the local static scope (a local static scope contains
+all fields present within the same scope, at the same nesting level).
+The dynamic scope prefixes are thus:
- Trace Packet Header: <trace.packet.header. >,
- Stream Packet Context: <stream.packet.context. >,