[lttng-dev] CTF semantics

[Milian Wolff]

Hey all,

I have looked through the CTF specification and ponder using it to replace my 
custom text-based output format of heaptrack.

At this stage, I have a fundamental question: How do the existing viewers like 
Trace Compass understand the semantics of the data? Or are the viewers not 
generic but instead rely on the existing generators like lttng? How does one 
know e.g. what the backtrace of a given event is?

In heaptrack's current format heavily interns data to greatly reduce the file 
size of the output data. This is crucial, and can be done with minimal 
overhead. So I'd like to do the same if and when I convert to using CTF. But 
how would e.g. know how to interpret that an integer member of a struct 
actually is an index into a list of backtraces?

Thanks
-- 
Milian Wolff | milian.wolff at kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5903 bytes
Desc: not available
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20160614/8155ee99/attachment-0001.bin>