[lttng-dev] [PATCH] Teach babeltrace understand "native" and "network" for byte_order

Yao Qi yao at codesourcery.com
Fri Mar 15 10:55:32 EDT 2013


On 03/15/2013 08:07 PM, Mathieu Desnoyers wrote:
> your interpretation of what the byte order should accept is based on
> section 4.1.3 of the CTF spec, which discusses what byte order can be
> accepted by a type.
>
> However, here you are proposing to change the byte order recognised at
> the trace declaration level. Unfortunately, we cannot assume anything
> about native endianness of the traced machine until we have the
> endianness information at the trace declaration level, as the trace can
> come from any source.

It is clear to me now.  Thanks for the clarification.

>
> Possibly that the CTF spec would need to be clarified. Currently, we
> need to look at:

The doc part is fine, but this error message is confusing,

[error] get_trace_byte_order: unexpected string "native". Should be 
"native", "network", "be" or "le".

Looks it was fixed.  When I update my tree, the error message is updated.

I'll give a comment in your comment to CTF spec.

-- 
Yao (齐尧)



More information about the lttng-dev mailing list