Project

General

Profile

Actions
Copy link

Bug #443

closed

byte_order values "native" and "network" are not recognized

Added by Simon Marchi about 11 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/13/2013
Due date:
% Done:

0%

Estimated time:

Description

When using byte_order = native in the trace stanza, as described in the CTF spec, babeltrace complains:

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

same for "network".

Actions
Copy link
 #1

Updated by Mathieu Desnoyers about 11 years ago

I think you misunderstood the CTF spec.

the trace {} section has:

byte_order = be OR le;                        /* Endianness (required) */

My guess is that you confused it with this section:

4.1.3 Byte order

which describes the values accepted by type declarations:

byte_order = native OR network OR be OR le;   /* network and be are aliases */

I agree that the warning message should be changed though, since it is misleading.

Thanks,

Mathieu

Actions
Copy link
 #2

Updated by Mathieu Desnoyers about 11 years ago

  • Status changed from New to Resolved

commit 33a3f20e5a8a5f6bc36c01a023ba49dd9d256f9a
Author: Mathieu Desnoyers <>
Date: Fri Feb 22 11:09:43 2013 -0500

Fix: warning message for unexpected trace byte order
Fixes #443
Signed-off-by: Mathieu Desnoyers &lt;&gt;
Actions
Copy link

Also available in: Atom PDF