Re: [lttng-dev] [RFC PATCH CTF 1/3] Clarify that unlisted enum values are implementation-defined

- Original Message - > From: "Mathieu Desnoyers" > To: "gbastien+lttng" , "Matthew Khouzam" > , > diamon-disc...@linuxfoundation.org, ppro...@efficios.com, "Jeremie Galarneau" > > Cc: "lttng-dev" , "Mathieu Desnoyers" > > Sent: Thursday, 23 April, 2020 16:52:24 > Subject: [RFC PATCH

Re: [lttng-dev] [RFC PATCH CTF 2/3] Clarify monotonicity requirement on timestamp begin

- Original Message - > From: "Mathieu Desnoyers" > To: "gbastien+lttng" , "Matthew Khouzam" > , > diamon-disc...@linuxfoundation.org, ppro...@efficios.com, "Jeremie Galarneau" > > Cc: "lttng-dev" , "Mathieu Desnoyers" > > Sent: Thursday, 23 April, 2020 16:52:25 > Subject: [RFC PATCH

Re: [lttng-dev] [RFC PATCH CTF 1/3] Clarify that unlisted enum values are implementation-defined

- Original Message - > From: "Mathieu Desnoyers" > To: "Philippe Proulx" > Cc: "gbastien+lttng" , "Matthew Khouzam" > , "Jeremie > Galarneau" , "lttng-dev" , > "diamon-discuss" > > Sent: Wednesday, 29 April, 2020 08:08:04 > Subject: Re: [RFC PATCH CTF 1/3] Clarify that unlisted enum

Re: [lttng-dev] babeltrace2: reading metadata + events from a single CTF file

On Mon, Sep 7, 2020 at 8:35 AM Dave Bort via lttng-dev wrote: > > Hello! I'm adding CTF-compatible tracing to a custom/experimental OS and have > a question: > > Can babeltrace2 read from a single CTF output file that contains both the > metadata stream and the binary trace streams? No. > >

Re: [lttng-dev] [barectf] Filter trace messages based on log level

On Tue, Oct 6, 2020 at 9:16 AM Owen, Mark (US) via lttng-dev wrote: > > Hi, > > Thank you for your work on barectf! Thank you for writing, Mark. I always appreciate getting feedback regarding barectf. > > I'm considering using it with our embedded MCUs that run on bare metal > in conjunction

Re: [lttng-dev] sink.ctf.fs vs bt_ctf_writer

Philippe Proulx On Mon, Aug 24, 2020 at 5:41 PM Michael Gruner via lttng-dev wrote: > > Hi all > > I’m integrating CTF support to a third party framework. To do so, I decided > to go with the Babeltrace 2 API (I love the rewrite BTW). Thank you. > So basically I made my custom plug-in and the

[lttng-dev] [RELEASE] barectf 3.0.0

Hi everybody. Today EfficiOS announces the release of barectf 3.0.0. barectf 3 is a major upgrade of the project which brings important additions and changes such as: * Support for static and dynamic array field types. * A reworked Python API. * A new YAML configuration schema. * An upgraded

Re: [lttng-dev] difference of timestamp between babeltrace and python binding

On Wed, Jul 22, 2020 at 9:17 AM Kim, Seongab via lttng-dev wrote: > > Hi, Hello. See my comments below. > > I found that the timestamps from babeltrace and python binding are different > in nanoseconds level. > > skim@d54030999178:~/ssd_work/traces$ python3 test.py ./trace/ | head -n 10 >

Re: [lttng-dev] LTTng event identification

On Thu, Aug 13, 2020 at 9:52 AM Valentin Grigorev via lttng-dev wrote: > > Hello! > > I'm using LTTng live session and Babeltrace 2 C API to analyze events > in online mode. > > I would like to route event processing statically (using IDs, without > parsing strings). And currently, I don't

Re: [lttng-dev] [EXTERNAL] Re: babeltrace cannot open the trace but Trace Compass can open

On Thu, Jul 23, 2020 at 5:09 AM Kim, Seongab wrote: > > Hello Phil, > > > -Original Message- > > From: Philippe Proulx > > Sent: Wednesday, July 22, 2020 5:06 PM > > To: Kim, Seongab > > Cc: lttng-dev@lists.lttng.org > > Subject: [EXTERNAL] Re: [lttng-dev] babeltrace cannot open the

Re: [lttng-dev] babeltrace cannot open the trace but Trace Compass can open

Thank you for the bug report. Can I kindly ask you to create an official issue for this? Go to . I'd also like you to attach the offending CTF trace so that I can analyze it if it doesn't contain sensitive data and is somewhat small. If

Re: [lttng-dev] [barectf] model.emf.uri

On Mon, Feb 1, 2021 at 4:39 AM RADERMACHER Ansgar via lttng-dev wrote: > > Hello, > > we're currently working on CTF code instrumentation in the C++ code > generation from Papyrus. Unlike in a previous version, we use BareCTF. > > In this context, the metadata tag "model.emf.uri" can contain the

Re: [lttng-dev] Usage example of libbabeltrace (babeltrace2) to read CTF traces from a GUI

- Original Message - > From: "Steven Rostedt" > To: "Philippe Proulx" > Cc: "Mathieu Desnoyers" , "Jeremie Galarneau" > , "lttng-dev" > , linux-trace-de...@vger.kernel.org > Sent: Tuesday, 15 June, 2021 11:57:38 > Subject: Re: [lttng-dev] Usage example of libbabeltrace (babeltrace2) to

Re: [lttng-dev] Usage example of libbabeltrace (babeltrace2) to read CTF traces from a GUI

On Mon, Jun 14, 2021 at 4:01 PM Mathieu Desnoyers via lttng-dev wrote: > > Hi Philippe, Hi Jeremie, > > Steven is interested to use libbabeltrace as a CTF trace reader in the > KernelShark > project. It's a GUI which shows Linux kernel traces. > > He notices that most of the documented usage

Re: [lttng-dev] [barectf] no nested types?

On Mon, Feb 8, 2021 at 5:27 AM RADERMACHER Ansgar via lttng-dev wrote: > > Dear all, > > having thought a bit more about it, I can see now that nested types are > problematic in general: some types in the language need to be mapped to types > that match but are not identical, i.e. have likely a

[lttng-dev] CTF2-SPECRC-3.0: Common Trace Format version 2 release candidate

Hello, This is an update of the CTF 2 specification release candidate from v2.0 to v3.0. This document, named CTF2-SPECRC-3.0, is available here: See the first section, "Revision history", to learn what changed. As always, please feel

[lttng-dev] CTF2-SPECRC-1.0: Common Trace Format version 2 release candidate

Hello, Today we're releasing the first release candidate of the Common Trace Format version 2 specification. This document, named CTF2-SPECRC-1.0, is available here: To write CTF2-SPECRC-1.0, many parts of CTF2-PROP-2.0rA [1] were

[lttng-dev] CTF2-SPECRC-2.0: Common Trace Format version 2 release candidate

Hello, This is an update of the CTF 2 specification release candidate from v1.0 to v2.0. This document, named CTF2-SPECRC-2.0, is available here: Although it's a major bump because there are breaking changes, there aren't a lot of changes

Re: [lttng-dev] [barectf] How to debug a malformed trace event?

Yoann, Sorry for the wait. I created a corresponding barectf project issue here: . Can you answer the latest question there? Thank you for reporting this. Philippe Proulx Philippe Proulx On Fri, Nov 26, 2021 at 12:41 PM Yoann Farré via

[lttng-dev] CTF 2: removal of the JSON text sequence auxiliary stream feature

Hello, Upon reflection, the JSON text sequence auxiliary streams of CTF2-SPECRC-4.0 [1] and data streams are redundant concepts considering that a CTF 2 data stream class may have a namespace and a name to identify it as containing specific/auxiliary data. Moreover, using data streams to

[lttng-dev] CTF2-SPECRC-4.0: Common Trace Format version 2 release candidate

Hello, This is an update of the CTF 2 specification release candidate from v3.0 to v4.0. This document, named CTF2-SPECRC-4.0, is available here: See the first section, "Revision history", to learn what changed. As always, please feel

[lttng-dev] CTF2-SPECRC-5.0

Hello, This is an update of the CTF 2 specification release candidate from v4.0 to v5.0. This document, named CTF2-SPECRC-5.0, is available here: See the first section, "Revision history", to learn what changed. As always, please feel

Re: [lttng-dev] Debugging Libaries in Babeltrace 2

On Wed, Oct 25, 2023 at 3:29 AM Seidl, Aron via lttng-dev wrote: > > Hi Simon, > Thanks for your quick answer! > I run GDB like this: > gdb --args ./babeltrace2 /home/aron/Schreibtisch/kernel4 -o text > (I'm in src/cli/.libs) > > I don't think I've ever installed a System Version of babeltrace2,

[lttng-dev] CTF2-SPECRC-8.0: Common Trace Format version 2 release candidate

Hello, This is an update of the CTF 2 specification release candidate from v7.0 to v8.0. This document, named CTF2-SPECRC-8.0, is available here: See the first section, "Revision history", to learn what changed. As always, please feel

Re: [lttng-dev] CTF2-SPECRC-5.0

see the "Revision history" section of CTF2-SPECRC-5.0 to learn more. Philippe Proulx EfficiOS Inc. https://www.efficios.com/ > > Thanks > Aprameya > > -Original Message- > From: lttng-dev On Behalf Of Philippe > Proulx > via lttng-dev > Sent: We

[lttng-dev] CTF2-SPECRC-6.0: Common Trace Format version 2 release candidate

Hello, This is an update of the CTF 2 specification release candidate from v5.0 to v6.0. This document, named CTF2-SPECRC-6.0, is available here: See the first section, "Revision history", to learn what changed. As always, please feel

Re: [lttng-dev] babeltrace2 python api related question

On Wed, Aug 10, 2022 at 9:54 AM zenan via lttng-dev wrote: > > > > Hi there, > > I’m trying to use babeltrace2 python bindings to track live lttng trace, as > shown in some examples in the documents, I tried to use ctf.lttng-live( > ctf.fs in the documents) plugin as source, and use text.pretty

Re: [lttng-dev] babeltrace2 python api related question

On Sun, Aug 14, 2022 at 4:48 AM zenan wrote: > > In command line, I use “babeltrace2 net://somehost/some-session” to read live > lttng session trace, and I want to use python bindings to do the same, is it > possible? > > here is my code: Almost there. Some `src.ctf.lttng-live` component and

[lttng-dev] CTF2-SPECRC-7.0: Common Trace Format version 2 release candidate

Hello, This is an update of the CTF 2 specification release candidate from v6.0 to v7.0. This document, named CTF2-SPECRC-7.0, is available here: See the first section, "Revision history", to learn what changed. As always, please feel

[lttng-dev] CTF2-SPECRC-9.0: Common Trace Format version 2 release candidate

Hello, This is an update of the CTF 2 specification release candidate from v8.1 to v9.0. This document, named CTF2-SPECRC-9.0, is available here: See the first section, "Revision history", to learn what changed. As always, please feel

[lttng-dev] Access specific fields from metadata file

Replying to an email from Volodymyr Fialko which was mistakenly erased. > Hello all, > > I'm trying to parse metadata file only, to get information about all > possible trace points. I'm using "Inspect event classes" example: >

Re: [lttng-dev] error with ctf_sequence_text when using non-utf8 encoded strings

On Wed, Jan 31, 2024 at 12:58 PM Nathan Ricci via lttng-dev wrote: > > I am trying to emit a trace that has a wchar string, using as one of the > fields ctf_sequence_text. When the trace is recorded, it seems like > everything at but the first character is truncated, and I think this is >

[lttng-dev] Upcoming CTF 2 specification

To those concerned, After years of development, the DiaMon Workgroup announces that it will publish the official specification of the Common Trace Format, version 2 based on its latest release candidate, CTF2-SPECRC-9.0 [1]. Indeed, we now possess sufficient implementation code to be very

[lttng-dev] [CTF2-SPEC-2.0] Announcing CTF 2, the next generation of the Common Trace Format

To all tracing enthusiasts, The Diagnostic and Monitoring Workgroup (DiaMon) is thrilled to announce the launch of version 2 of the Common Trace Format (CTF), a binary trace format designed to be fast to write without compromising great flexibility. The first version of CTF [1] has been widely