Difference between revisions of "GstShark - Common Trace Format files"
m |
m |
||
| Line 1: | Line 1: | ||
| − | {{GstShark/Head |previous=Results|next=Pipeline Diagram|metakeywords=}} | + | {{GstShark/Head |previous=Results|next=Pipeline Diagram|metakeywords=Common Trace Format files, DiaMon, Common Trace Format, CTF}} |
The results of an analysis process by GstShark yields Common Trace Format (CTF) files. | The results of an analysis process by GstShark yields Common Trace Format (CTF) files. | ||
Latest revision as of 05:22, 16 March 2023
 | Open-source project from Ridgerun. |
| GstShark |
|---|
 |
| Getting Started |
| Generating trace files |
| Tracer Parameters |
| Available Tracers |
| Results |
| Visualization Tools |
| Examples |
| Contact Us |
The results of an analysis process by GstShark yields Common Trace Format (CTF) files.
Standard format of results
The Common Trace Format files yielded by GstShark comply with the specification described by the Diagnostic and Monitoring workgroup (DiaMon) of the Linux Foundation. Details on the format are described at the DiaMon website.
The Common Trace Format (CTF) describes a very fast, yet flexible way of storing trace data. The data is stored in binary format, making it easy to be generated by C/C++ programs and hardware devices.
