[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

[lttng-dev] Upcoming CTF 2 specification

stream attribute [2] or extension [3] instruments. [1]: https://diamon.org/ctf/files/CTF2-SPECRC-9.0rA.html [2]: https://diamon.org/ctf/files/CTF2-SPECRC-9.0rA.html#attrs [3]: https://diamon.org/ctf/files/CTF2-SPECRC-9.0rA.html#ext I hope you have a very good day, Philippe Proulx EfficiOS Inc

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

l need to decode it manually using the Babeltrace 2 API. I'll wait for your metadata text. Philippe Proulx > > liblttng-ust-common1/jammy,now 2.13.1-1ubuntu1 > > I’ve boiled this down to a simple repro; I’ve included the code below, but > you can also get it here: https://githu

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

ays, please feel free to provide feedback. Philippe Proulx EfficiOS Inc. ___ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

[lttng-dev] Access specific fields from metadata file

much more easily than with the metadata DSL (TSDL) of CTF 1.8. The latest specification RC is available here: <https://diamon.org/ctf/files/>. Babeltrace 2.1 and LTTng 2.15 will support CTF 2. BR, Philippe Proulx ___ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

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

ays, please feel free to provide feedback. Philippe Proulx EfficiOS Inc. ___ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

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

ays, please feel free to provide feedback. Philippe Proulx EfficiOS Inc. ___ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

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

gt; # to the `in` input port of the `sink.text.pretty` component. > graph.connect_ports(src_comp.output_ports['out'], sink_comp.input_ports['in']) > > # Run the trace processing graph. > graph.run() > > > > > > 发件人: Philippe Proulx > 发送时间: 2022年8月10日 22:08 >

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

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

ays, please feel free to provide feedback. Philippe Proulx EfficiOS Inc. https://efficios.com/ ___ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

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

- Original Message - > From: "Aprameya Rao" > To: "Philippe Proulx" , "diamon-discuss" > , "Eric Warden" > > Cc: "lttng-dev" , "tracecompass-dev" > > Sent: Wednesday, 6 April, 2022 20:51:33 > Subject:

[lttng-dev] CTF2-SPECRC-5.0

ays, please feel free to provide feedback. Philippe Proulx EfficiOS Inc. https://efficios.com/ ___ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

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

don't want such data to show up in the output of a Babeltrace 2 `sink.text.pretty` component or in the events editor of Trace Compass. Should you have any issue with this approach, please reply to this email to illustrate your point of view. Have a good day, Philippe Proulx EfficiOS Inc. http

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

ays, please feel free to provide feedback. Philippe Proulx EfficiOS Inc. https://efficios.com/ ___ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

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

ays, please feel free to provide feedback. Philippe Proulx EfficiOS Inc. https://efficios.com/ ___ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

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

hanges since CTF2-SPECRC-1.0. See the first section, "Revision history", to learn what changed. As always, please feel free to provide feedback. Philippe Proulx EfficiOS Inc. https://efficios.com/ ___ lttng-dev mailing list lttng-dev@lists

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

Yoann, Sorry for the wait. I created a corresponding barectf project issue here: <https://github.com/efficios/barectf/issues/19>. 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] CTF2-SPECRC-1.0: Common Trace Format version 2 release candidate

coding a streamed version of such input easier using any JSON parser, for example to meet the needs of use cases similar to LTTng live [3]. Feel free to provide feedback! Philippe Proulx EfficiOS Inc. https://efficios.com/ [1]: https://diamon.org/ctf/files/CTF2-PROP-2.0rA.html [2]:

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 &g

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

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] [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

[lttng-dev] [RELEASE] barectf 3.0.0

documentation website [1]. This documentation project also shows how to install barectf 3 using pip [2]. We wish you a good day. Philippe Proulx EfficiOS Inc. https://www.efficios.com/ [1]: https://barectf.org/docs/barectf/3.0/whats-new.html [2]: https://barectf.org/docs/barectf/3.0/install.html

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] 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 m

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: [EXT

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] 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] [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: We

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: "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] Need help with CTF

On Fri, Jul 12, 2019 at 2:04 AM Ravindra Kumar Meena wrote: > > Hi developers, > > trace { > major = 1; > minor = 8; > uuid = "6a7715d0-b502-4c65-8678-6777ac7f755a"; > byte_order = le; > packet.header := struct { > uint32_t magic; > uint8_t uuid[16]; >

Re: [lttng-dev] (no subject)

On Wed, Jun 12, 2019 at 11:22 PM Zvi Vered wrote: > > Hello, > > I'm trying to read the file "metadata". > I read the struct: > > struct metadata_packet_header { > uint32_t magic; /* 0x75D11D57 */ > uint8_t uuid[16]; /* Unique Universal Identifier */ > uint32_t checksum; /* 0 if unused */ >

Re: [lttng-dev] [PATCH lttng-ust v2] Add setuid wrappers for per-UID buffers

On Wed, Jun 5, 2019 at 2:57 PM Gabriel-Andrew Pollo-Guilbert wrote: > > diff --git a/doc/man/lttng-ust.3.txt b/doc/man/lttng-ust.3.txt > index 5c9c9f5d..d58b43c7 100644 > --- a/doc/man/lttng-ust.3.txt > +++ b/doc/man/lttng-ust.3.txt > @@ -744,6 +744,17 @@ library before you start the application.

Re: [lttng-dev] [tracecompass-dev] Scalability

On Wed, Mar 13, 2019 at 10:14 AM Doug Schaefer wrote: > > I'll use the patch . > > I was somewhat following the CTF Writer API python example which > implied I could use the original. Is that not the case? Yes it's the case, but there was a bug! Phil > > Thanks! > Doug > > >

Re: [lttng-dev] [tracecompass-dev] Scalability

On Wed, Mar 13, 2019 at 8:46 AM Doug Schaefer wrote: > > Very cool. Would explicitly setting the byte order for each field be a short > term workaround? You found a very specific scenario highlighting this bug. Some field types are copied behind the scenes for resolving purposes. This is done

Re: [lttng-dev] [tracecompass-dev] Scalability

On Wed, Mar 13, 2019 at 8:13 AM Matthew Khouzam wrote: > > Hi Doug & Efficios, > > > I suspect the issue is with libbabeltrace-ctf. When opening the trace in > Trace Compass, it failed saying the sequence was 2gb big. When opening in > babeltrace, it OOMed with 2gb allocations. When opening

Re: [lttng-dev] "Hands-free" tracepoints using LD_PRELOAD

On Fri, Jan 25, 2019 at 4:05 AM Brian Rossa wrote: > > Francis, > > These are great suggestions, thanks! > >> #Third idea: >> Do you know of tracef() [3] ? Using it, you can save any string to a >> UST trace. As a first step, you could directly replace your calls to >> spdlog by calls to tracef.

Re: [lttng-dev] TP_ARGS for TRACEPOINT_EVENT_CLASS and TRACEPOINT_EVENT_INSTANCE

On Thu, Dec 20, 2018 at 11:47 AM Yonghong Yan wrote: > > I am looking at the following example from lttng-ust manual. The same TP_ARGS > ( ... ) are repeated in both the TRACEPOINT_EVENT_CLASS and > TRACEPOINT_EVENT_INSTANCE definition. My understanding is that it actually > allows using

Re: [lttng-dev] How can I get traces in live mode from lttng in my c++ application without using tcp sockets?

get-traces-in-live-mode-from-lttng-in-my-c-application-without-using#comment92560450_52818181>. Philippe Proulx > ___ > lttng-dev mailing list > lttng-dev@lists.lttng.org > https://lists.lttng.org/c

Re: [lttng-dev] User Space Tracing

In `resolution_management_tp.tp`, can you try using the exact same `TP_ARGS` content for both `TRACEPOINT_EVENT_INSTANCE` (also matching the `TP_ARGS` content of `TRACEPOINT_EVENT_CLASS`)? It's the only difference I can see. Philippe Proulx Philippe Proulx On Thu, Sep 27, 2018 at 12:15 PM John

Re: [lttng-dev] Proposal: Make lttng-analyses part of lttng-tools

On Wed, Jul 18, 2018 at 11:37 AM Geneviève Bastien wrote: > > > I'm eager to get some feedback from Mathieu and Jérémie on all this. > So am I! Adding mine even if you're not eager to get it ;-). As someone who knows a few parts of the LTTng analyses project, it is still considered

Re: [lttng-dev] Processing large trace files

On Tue, Jul 10, 2018 at 11:33 AM Shehab Elsayed wrote: > > I haven't tried the C API yet. > > A smaller trace of about 2.7GB took +5 hrs before I had to kill the process. Wow. The Python bindings are slow by nature, but that's a lot of time! > > As for trace cutting, that sounds promising. How

Re: [lttng-dev] cannot find lttng/tracepoint.h

On Sat, May 12, 2018 at 7:12 PM, Francesco Mariniello wrote: > > Hi lttng dev, > i'm a student writing my final paper on lttng, i'm currently trying to run > the example from the > https://lttng.org/docs/v2.10/#doc-tracing-your-own-user-application > > but when i

Re: [lttng-dev] [RFC babeltrace 1/2] fs-src: add argument for metadata src dir

On Tue, May 1, 2018 at 11:12 AM, Alexander Aring <ar...@mojatatu.com> wrote: > Hi, > > On Mon, Apr 30, 2018 at 06:36:08PM -0400, Philippe Proulx wrote: >> On Mon, Apr 30, 2018 at 5:31 PM, Alexander Aring <ar...@mojatatu.com> wrote: >> > >> > This

Re: [lttng-dev] [RFC babeltrace 0/2] fs-src: add metadata-src parameter

wrote: > Hi, > > On Mon, Apr 30, 2018 at 07:11:30PM -0400, Philippe Proulx wrote: >> On Mon, Apr 30, 2018 at 5:31 PM, Alexander Aring <ar...@mojatatu.com> wrote: >> > Hi, >> > >> > my use-case is just... we have several application with the same

Re: [lttng-dev] [RFC babeltrace 1/2] fs-src: add argument for metadata src dir

On Mon, Apr 30, 2018 at 6:36 PM, Philippe Proulx <eeppelitel...@gmail.com> wrote: > On Mon, Apr 30, 2018 at 5:31 PM, Alexander Aring <ar...@mojatatu.com> wrote: >> >> This patch adds an argument for the fs-src plugin to declare the >> directory to find the

Re: [lttng-dev] [RFC babeltrace 0/2] fs-src: add metadata-src parameter

On Mon, Apr 30, 2018 at 5:31 PM, Alexander Aring wrote: > Hi, > > my use-case is just... we have several application with the same metadata > file. Currently I build a wrapper around babeltrace to run something like: > > find $(TRACE_DIR}/* -maxdepth 1 -type d -exec cp >

Re: [lttng-dev] [RFC babeltrace 1/2] fs-src: add argument for metadata src dir

On Mon, Apr 30, 2018 at 5:31 PM, Alexander Aring wrote: > > This patch adds an argument for the fs-src plugin to declare the > directory to find the metadata file instead of placing it in every > subdir of traces. > > If parameter assign every subdirectory which does not have

Re: [lttng-dev] Problem in finding Jar file of LTTng for adding to Java project

ks a lot for your consideration. I solved former problem. While, I > >>>> faced with a new problem. Indeed, when I create a LTTng session, start > >>>> it and finally stop LTTng, I could not find trace files in mentioned > >>>> folder. My java code is > &g

Re: [lttng-dev] Problem in finding Jar file of LTTng for adding to Java project

> [error] none of the specified trace paths could be opened. This is because your trace is empty (does not even exist). Phil > > Could you please help me to resolve it. > > Regards, > Mehdi. > > > > > > > > > > On Monday, October 9, 2017, 1:05:59 AM GMT+3:30, Phi

Re: [lttng-dev] Problem in finding Jar file of LTTng for adding to Java project

On Sun, Oct 8, 2017 at 4:15 PM, MMM via lttng-dev wrote: > Dear Users, > > I am beginner in tracing using LTTng. At present, I am going to trace a java > program in Ubuntu, while I faced with a problem. When I install LTTng on > Ubuntu, I also install > >

Re: [lttng-dev] Are arrays allowed in event payload?

On Mon, Sep 25, 2017 at 3:41 PM, Nwafor, Ebelechukwu wrote: > Hello All > > I am new to barectf. I am trying to define my yaml configuration and i keep > getting an error whenever i try to compile my configuration. I was wondering > if arrays are allowed in

Re: [lttng-dev] Check if userland tracing enabled

On Fri, Sep 22, 2017 at 10:06 AM, Simon Crowe wrote: > All, > > I am looking a userland C program, but i want the application to do a little > extra work when there is a tracing session active, is there fast call I > could use which would tell me if a tracing session is in

Re: [lttng-dev] babeltrace tests (master/2.0)

On Fri, Sep 15, 2017 at 3:53 PM, Nathan Lynch <nathan_ly...@mentor.com> wrote: > Nathan Lynch <nathan_ly...@mentor.com> writes: >> Philippe Proulx <eeppelitel...@gmail.com> writes: >>> >>> I asked the Automake mailing list about this >>> <ht

Re: [lttng-dev] liblttng-ust overhead, take 2

On Thu, Sep 7, 2017 at 1:55 PM, Mathieu Desnoyers wrote: > Also, please note that lttng-modules exposes a /proc/lttng-logger > file, into which you can write from user-space. It ends up in the > kernel trace. This could do the trick if for some reason lttng-ust >

Re: [lttng-dev] Status of MinGW support for babeltrace (either 1.x or 2.x)

On Tue, Aug 15, 2017 at 2:25 PM, Jonah Graham <jo...@kichwacoders.com> wrote: > > > On 15 Aug 2017 19:10, "Philippe Proulx" <eeppelitel...@gmail.com> wrote: > > On Tue, Aug 15, 2017 at 1:09 PM, Jonah Graham <jo...@kichwacoders.com> > wrote: >> T

Re: [lttng-dev] Status of MinGW support for babeltrace (either 1.x or 2.x)

xisting trace format to CTF? Phil > > We'll do what we can to provide patches. > > Thanks, > Jonah > > On 15 Aug 2017 17:39, "Philippe Proulx" <eeppelitel...@gmail.com> wrote: >> >> On Tue, Aug 15, 2017 at 12:12 PM, Jonah Graham <jo...@kichwac

Re: [lttng-dev] Status of MinGW support for babeltrace (either 1.x or 2.x)

On Tue, Aug 15, 2017 at 12:12 PM, Jonah Graham wrote: > > Hello, > > Over the years I have seen some discussions and patches about getting > full MinGW support for babeltrace. I am interested in if someone can > provide an overview of the current state of MinGW. > > I have

Re: [lttng-dev] babeltrace tests (master/2.0)

; other >> projects I've checked just have one top-level definition of TESTS. >> >> I'm aware of the rationale for doing it this way: >> >> commit 6ca1931cb32ca2eb33252896d2a42a4c48af436a >> Author: Philippe Proulx <eeppelitel...@gmail.com> >> Date: Fri May 5 16:4

Re: [lttng-dev] lttng questions

On Sun, Jul 16, 2017 at 2:28 PM, Nalin Pai wrote: > > Hello, > > We are looking at using lttng as a solution for all our trace and debug > requirements. We want to get away from traditional file based string format > logging and move to lttng, which then gives us the

Re: [lttng-dev] lost events in a trace

On Mon, Jun 12, 2017 at 6:21 PM, Deneau, Tom wrote: > > I am using the babeltrace python3 bindings on a trace collected with > event-loss-mode > set to discard. The tracecollection is a combination of a kernel channel and > a usermode > channel. How can I tell whether there

Re: [lttng-dev] porting LTTng to Go(lang)?

ot been assigned to get LTTng to > work in Go, so this is all quite preliminary. but i think the project i'm > about to start on really needs LTTng or LTTng-like tracepoint functionality > so i'm motivated to see if this can work. > > i'm going to investigate some more. > > --

Re: [lttng-dev] Explicit setting of UUID with ctf writer

you want to analyze this combination ultimately? By the way, babeltrace(1) 2.0.0 will be able to combine different format of traces from different sources as a single CTF trace like you want to do. Phil > > Thanks, > Rocky > > On Fri, Apr 7, 2017 at 3:03 PM, Philippe Proulx <eeppe

Re: [lttng-dev] Explicit setting of UUID with ctf writer

ription are supported by > this babeltrace version. > [error] Opening CTF traces for output is not supported yet. > Error opening trace "combined" for writing. Did you try with --clock-force-correlate? Phil > > Thanks, > Rocky > > On Fri, Apr 7, 2017 at 3:03 PM, Phili

Re: [lttng-dev] Explicit setting of UUID with ctf writer

in the chosen `metadata` file with the canonical representation of your favorite UUID. Phil > > Rocky > > On Apr 7, 2017 1:57 PM, "Philippe Proulx" <eeppelitel...@gmail.com> wrote: >> >> On Fri, Apr 7, 2017 at 3:18 PM, Rocky Dunlap <rsdunla...@gmail.com>

Re: [lttng-dev] Explicit setting of UUID with ctf writer

On Fri, Apr 7, 2017 at 3:18 PM, Rocky Dunlap wrote: > Is it possible to explicitly set a uuid for a trace using the Babeltrace CTF > writer? I did not see a straightforward way to do it with the API. It's not possible as of Babeltrace 1. We'll add trace UUID accessors to

Re: [lttng-dev] [PATCH lttng-modules] Fix formatting in strutils_star_glob_match_char_cb explanation

<francis.deslauri...@efficios.com> Signed-off-by: Philippe Proulx <eeppelitel...@gmail.com> > --- > lttng-string-utils.c | 108 > +-- > 1 file changed, 54 insertions(+), 54 deletions(-) > > diff --git a/lttng-strin

Re: [lttng-dev] [PATCH lttng-tools] Fix: free previous instance of url (alloc_url) on default live url assignation

On Mon, Dec 12, 2016 at 4:16 PM, Jonathan Rajotte wrote: > > Signed-off-by: Jonathan Rajotte > --- > src/bin/lttng/commands/create.c | 6 ++ > 1 file changed, 6 insertions(+) > > diff --git

Re: [lttng-dev] CTF2-PROP-1.0: Proposal for a major revision of the Common Trace Format, version 1.8

- Original Message - > From: "Jérémie Galarneau" <jeremie.galarn...@efficios.com> > To: "Philippe Proulx" <ppro...@efficios.com> > Cc: "diamon-discuss" <diamon-disc...@lists.linuxfoundation.org>, "lttng-dev" > <lttng

Re: [lttng-dev] [lttng-tools] changelog question

On Mon, Nov 28, 2016 at 11:11 AM, Sebastien Boisvert <sboisv...@gydle.com> wrote: > > > On 28/11/2016 17:00, Philippe Proulx wrote: >> On Mon, Nov 28, 2016 at 10:12 AM, Sebastien Boisvert >> <sboisv...@gydle.com> wrote: >>> Hi Jérémie, &

Re: [lttng-dev] [lttng-tools] changelog question

On Mon, Nov 28, 2016 at 10:12 AM, Sebastien Boisvert wrote: > Hi Jérémie, > > > In the ChangeLog of lttng-tools at > > > http://git.lttng.org/?p=lttng-tools.git;a=blob_plain;f=ChangeLog;hb=bfa0fdc125195ca4fc1716a6d521f0dfe7bc90d0 > > > Is it normal that there is no entry

Re: [lttng-dev] [barectf] Building /w. Microsoft Visual Studio

On Tue, Nov 15, 2016 at 9:05 AM, Jean-Francois MONESTIER <jean-francois.monest...@st.com> wrote: > Hello Philippe, > > Thank you for your prompt response ! > > Le 10/11/2016 à 22:56, Philippe Proulx a écrit : >>> I removed the dependency on __typeof__() and statement

Re: [lttng-dev] [barectf] Building /w. Microsoft Visual Studio

On Thu, Nov 10, 2016 at 1:25 PM, Philippe Proulx <eeppelitel...@gmail.com> wrote: > On Thu, Nov 10, 2016 at 12:17 PM, Jean-Francois MONESTIER > <jean-francois.monest...@st.com> wrote: >> Hello Tracers ! >> >> I'm currently having hard times, trying to bui

Re: [lttng-dev] [barectf] Building /w. Microsoft Visual Studio

On Thu, Nov 10, 2016 at 12:17 PM, Jean-Francois MONESTIER wrote: > Hello Tracers ! > > I'm currently having hard times, trying to build a barectf-generated CTF > writer with Microsoft Visual Studio 2008. > > Problem resides in the .._bitfield.h file, macro >

Re: [lttng-dev] [barectf] Request for C++ compatible source

On Wed, Nov 9, 2016 at 11:18 AM, Rocky Dunlap wrote: > Great work on the barectf tool! This really makes it easy to write out CTF. > > I would like to integrate the generated code into a larger project that, for > historical reasons, uses the C++ compiler. Would it be

Re: [lttng-dev] CTF2-PROP-1.0: Proposal for a major revision of the Common Trace Format, version 1.8

- Original Message - > From: "Jérémie Galarneau" <jeremie.galarn...@efficios.com> > To: "Philippe Proulx" <ppro...@efficios.com> > Cc: "diamon-discuss" <diamon-disc...@lists.linuxfoundation.org>, "lttng-dev" > <lttng

Re: [lttng-dev] [PATCH lttng-ust] Implement LTTNG_UST_BLOCKING_RETRY_TIMEOUT

On Fri, Nov 4, 2016 at 9:44 AM, Mathieu Desnoyers wrote: > +`LTTNG_UST_BLOCKING_RETRY_TIMEOUT`:: > +Maximum time during which event tracing retry is attempted on buffer > +full condition (millliseconds). Setting this environment to non-zero > +value

Re: [lttng-dev] [PATCH lttng-ust] Implement LTTNG_UST_BLOCKING_RETRY_TIMEOUT

On Fri, Nov 4, 2016 at 10:23 AM, Jonathan Rajotte Julien <jonathan.rajotte-jul...@efficios.com> wrote: > > > On 2016-11-04 10:22 AM, Philippe Proulx wrote: >> >> On Fri, Nov 4, 2016 at 10:13 AM, Jonathan Rajotte Julien >> <jonathan.rajotte-jul...@eff

Re: [lttng-dev] [PATCH lttng-ust] Implement LTTNG_UST_BLOCKING_RETRY_TIMEOUT

On Fri, Nov 4, 2016 at 10:13 AM, Jonathan Rajotte Julien wrote: > > Nitpicking: > > Should this be RETRY_DELAY_MS since other name scheme use the *_MS suffix ? > > e.g: > LTTNG_UST_RING_BUFFER_RETRY_DELAY_MS >

[lttng-dev] Create virtual LTTng environments with vlttng (blog post)

ons of the LTTng, Babeltrace, and Trace Compass projects without having to read any doc about how to build and install them. Have fun, Philippe Proulx EfficiOS Inc. http://www.efficios.com/ ___ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.l

Re: [lttng-dev] Babeltrace python bindings documentation is no up-to-date

On Mon, Oct 31, 2016 at 4:38 PM, Philippe Proulx <eeppelitel...@gmail.com> wrote: > On Mon, Oct 31, 2016 at 4:02 PM, Jean Spector <jean.spec...@gmail.com> wrote: >> Thank you Philippe. >> >> Adding a different documentation page for older versions (it's the lates

Re: [lttng-dev] Babeltrace python bindings documentation is no up-to-date

- RHEL 7.2 > > > In any case, thanks for the great tool. I hope to put it to good use. > Jean Thanks for the feedback! We appreciate. Phil > > > On Mon, Oct 31, 2016 at 7:07 PM, Philippe Proulx <eeppelitel...@gmail.com> > wrote: >> >> On Sat, Oct 29

Re: [lttng-dev] Babeltrace python bindings documentation is no up-to-date

On Sat, Oct 29, 2016 at 9:55 AM, Jean Spector wrote: > When trying to use the example from > http://diamon.org/babeltrace/docs/python/examples/ (pointed to via > http://lttng.org/viewers/), the code is not up-to-date. > > For instance, the first line in the example (import

Re: [lttng-dev] babeltrace API question

On Sat, Oct 29, 2016 at 5:35 PM, Sebastien Boisvert wrote: > Hi, > > > I would like to add filter options to babeltrace. > > I am exploring the babeltrace API. I would strongly advise you NOT to use this API as we're about to deprecate it in a few weeks when Babeltrace 2.0

Re: [lttng-dev] [tracecompass-dev] CTF2-PROP-1.0: Proposal for a major revision of the Common Trace Format, version 1.8

ass-dev] CTF2-PROP-1.0: Proposal for a major revision > of the Common Trace Format, version 1.8 > On 16-10-25 02:26 PM, Philippe Proulx wrote: >> A few things that still annoy me: >> >> * Should a boolean field type inherit the properties of an integer field >&g

Re: [lttng-dev] CTF2-BASICATTRS-1.0: Basic CTF 2 user attributes

Philippe Proulx On Tue, Oct 25, 2016 at 2:27 PM, Philippe Proulx <ppro...@efficios.com> wrote: > > [[event-record-class-fragment-bua]] > == Event record class fragment's basic user attributes > > .Event record class fragment's basic user attributes mdt:map properti

[lttng-dev] CTF2-PMETA-1.0: CTF 2 packetized metadata stream format

HTML version: http://diamon.org/ctf/files/CTF2-PMETA-1.0.html Philippe Proulx EfficiOS Inc. http://www.efficios.com/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - = CTF2-PMETA-1.0: CTF{nbsp}2 packetized metadata stream format Philippe Proulx <ppro...@efficios.

[lttng-dev] CTF2-BASICATTRS-1.0: Basic CTF 2 user attributes

HTML version: http://diamon.org/ctf/files/CTF2-BASICATTRS-1.0.html Philippe Proulx EfficiOS Inc. http://www.efficios.com/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - = CTF2-BASICATTRS-1.0: Basic CTF{nbsp}2 user attributes Philippe Proulx <ppro...@efficios.

Re: [lttng-dev] Problem with Babeltrace

On Mon, Oct 24, 2016 at 11:35 AM, Simon Marchi wrote: > On 2016-10-24 11:31, Nathan Lynch wrote: >> >> On 10/24/2016 03:30 AM, Tim Tannert wrote: >>> >>> Hey, >>> >>> everytime when I start babeltrace: >>> *babeltrace --version* >>> >>> or >>> *lttng view >>> >>> *I'll get

Re: [lttng-dev] A question about lttng view and babeltrace

On Mon, Oct 24, 2016 at 4:08 AM, Sebastien Boisvert wrote: > Hello, > > > I am using this to generate my text trace: > > >path=`lttng list $sessionName|grep path|awk '{print $3}'` >textFile=$sessionName.txt >babeltrace --clock-seconds $path > $textFile

Re: [lttng-dev] [lttng-ust] [babeltrace] use case question - field names in event classes

On Tue, Oct 11, 2016 at 4:46 PM, Staffan Tjernstrom wrote: > We have a situation where we have a significant number (1000's) of > log-style trace messages generated by a large group of (sometime > offsite) developers. > > Unfortunately the tracepoint definitions are

Re: [lttng-dev] sdt.h tracepoints with unicode data and/or structs

>> This sounds excellent. Can you tell me how? Could you maybe add an example to >> lttng-ust. Also note how http://lttng.org/man/3/lttng-ust/v2.7 says: >> >> if (tracepoint_enabled(ust_tests_hello, tptest)) { >> /* prepare arguments */ >>

Re: [lttng-dev] [PATCH lttng-tools] Cleanup: Remove fun from code base

Finally this project is getting serious! Philippe Proulx On Tue, Sep 27, 2016 at 3:13 PM, Jérémie Galarneau <jeremie.galarn...@efficios.com> wrote: > Fun removed from master, thanks... ;) > > Jérémie > > On 25 September 2016 at 14:32, Mathieu Desnoyers > <mathieu.de

Re: [lttng-dev] sdt.h tracepoints with unicode data and/or structs

uld then convert it to UTF8 offline, if needed. >> > >> > The advantage here is that I have "zero" overhead while tracing, which is >> > crucial for me to get the tracepoints accepted upstream in Qt, without >> > hiding them behind a compiler switch. >

Re: [lttng-dev] Beginner question: how to inspect scheduling of multi-threaded user application?

On Mon, Sep 19, 2016 at 11:38 AM, David Aldrich wrote: > > Hi Jonathan > > Thanks for your reply. What is 'comm' in 'prev_comm'? "comm" stands for "command". See this in sched.h: /* Task command name length */ #define TASK_COMM_LEN 16 Phil > > Best regards

Re: [lttng-dev] Babeltrace, Python3, and the Event Declarations

On Wed, Jul 20, 2016 at 12:45 PM, Thibault, Daniel wrote: >I'm tinkering with the Python 3 bindings for babeltrace, and I've come > upon an odd feature: for a given trace, if I ask for the EventDeclarations > (using the TraceHandle), I end up getting the set

  1   2   >