From: Mathieu Desnoyers Date: Wed, 4 May 2011 19:58:12 +0000 (-0400) Subject: Explain limitations if packet header fields are not present X-Git-Tag: v1.8~58 X-Git-Url: http://git.efficios.com/?p=ctf.git;a=commitdiff_plain;h=37b39e474c20f68d8e9321b2cd8f296488bf59f5;ds=sidebyside Explain limitations if packet header fields are not present Signed-off-by: Mathieu Desnoyers --- diff --git a/common-trace-format-proposal.txt b/common-trace-format-proposal.txt index f2f7e23..8182ea9 100644 --- a/common-trace-format-proposal.txt +++ b/common-trace-format-proposal.txt @@ -597,6 +597,17 @@ trace { packet.header := struct event_packet_header; }; +If a packet header lacks the "magic" number field, the trace endianness +needs to be specified in the trace "endian" metadata attribute. + +If the trace_uuid is not present, no validation that the metadata +actually corresponds to the stream is performed. + +If the stream_id packet header field is missing, the trace can only +contain a single stream. Its "id" field can be left out, and its events +don't need to declare a "stream_id" field. + + 5.2 Event Packet Context Description Event packet context example. These are declared within the stream declaration