Event Recording/CTF: Get closer to LTTNG output

Ravindra Kumar Meena rmeena840 at gmail.com
Fri Jul 12 03:58:03 UTC 2019


>
> Why don't you simply use the above in your C code as well?
>>
> Yes. I tried that but compiler reports the value is too large.
> ../misc/record/record-main.c:357:27: warning: integer constant is too
> large for its type
>      ctf_header.uuid[16] = 0x6a7715d0b5024c6586786777ac7f755a;
>

Okay. I was thinking in the wrong direction. I have now added uuid also in
the stream header.

https://github.com/rmeena840/rtems-tools/commit/fa17148220dfd9a1df1f3d8cfad0b4afd19c331f

https://github.com/rmeena840/rtems-tools/commit/05dbb29c72a5cceee054a996a8e799520d7b2817

Tested on AWS. No warnings.

In the packet.header you mentioned to added stream_instance_id. See below.
What is it? In the documentation it is mentioned that packet.header can
only contain three values(magic, uuid, stream_id).

trace {
        major = 1;
        minor = 8;
        uuid = "6a7715d0-b502-4c65-8678-6777ac7f755a";
        byte_order = le;
        packet.header := struct {
                uint32_t magic;
                uint8_t  uuid[16];
                uint32_t stream_id;
                uint64_t stream_instance_id;
        };
};


-- 
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190712/575b4a4a/attachment-0002.html>


More information about the devel mailing list