Re: [lttng-dev] bt2 Python quick start/examples?

On 2020-03-12 10:18 a.m., Jonathan Rajotte-Julien via lttng-dev wrote: > Hi, > > On Wed, Mar 11, 2020 at 10:56:24PM -0400, Rocky Dunlap via lttng-dev wrote: >> I see that the bt2 Python documentation is not yet ready: >> https://babeltrace.org/docs/v2.0/python/bt2/ > > Slowly getting there. > >>

Re: [lttng-dev] Babeltrace2 - compilation error with intel18

On 2020-03-20 5:10 p.m., Rocky Dunlap via lttng-dev wrote: > I am trying to compile BT2 with Python bindings using Intel18.  I receive the > following error during the build: Hi Rocky, I don't think we claim to support the Intel compiler, so you might be a bit on your own here. Although if you w

Re: [lttng-dev] Babeltrace2 - compilation error with intel18

On 2020-03-20 5:55 p.m., Rocky Dunlap wrote: > Simon, > > I was able to get past the issue by passing "--enable-compile-warnings=yes" > to configure. > > It get a lot further, then fails here: > > gcc -pthread -shared -L/apps/intel/intelpython3/lib > -Wl,-rpath=/apps/intel/intelpython3/lib,--n

Re: [lttng-dev] Babeltrace2 - compilation error with intel18

On 2020-03-20 6:32 p.m., Rocky Dunlap via lttng-dev wrote: > Simon, > > Thanks for this - so after I updated to gcc 9.2, the shared libraries command > ran correctly and the build finished. All the tests pass and I was able to > read in a CTF trace from a python script.   > > The issue was that

Re: [lttng-dev] Babeltrace2 - compilation error with intel18

On 2020-03-20 11:12 p.m., Simon Marchi via lttng-dev wrote: > So since distutils really wants to compile the Python native modules using > all the same > flags as the Python interpreter was built with, I presume that they really > assume that > you'll be using the exact sam

Re: [lttng-dev] Babeltrace2 - compilation error with intel18

On 2020-03-23 12:05 p.m., Rocky Dunlap wrote: > Simon, > > Yes, I will be happy to give this a try.  What's the easiest way to get this > patch?  (Sorry, I'm less familiar with Gerrit...) > > Rocky You need a babeltrace git repository. If you don't already have one, you can clone it from here

Re: [lttng-dev] Babeltrace2 - compilation error with intel18

On 2020-03-23 12:56 p.m., Rocky Dunlap wrote: > Simon, > > Success!  This change worked and I was able to build and install with icc.  > Thank you! Ok, thanks. Out of curiosity, did run a "make check"? That would validate that the Python bindings (and everything else) works properly. > I stil

Re: [lttng-dev] babletrace2 graph performance considerations

On 2020-03-30 12:10 a.m., Rocky Dunlap via lttng-dev wrote: > A couple of questions on performance considerations when setting up bt2 > processing graphs. > > 1.  Do parts of the processing graph that can execute concurrently do so?  > Does the user have any control over this, e.g., by creating

Re: [lttng-dev] bt2 python - accessing component instances added to graph

On 2020-03-30 1:24 a.m., Rocky Dunlap via lttng-dev wrote: > I noticed that when I add a component to a bt2 graph, e.g.: > > sink = g.add_component(SinglePETSink, "sink"+str(idx)) > > The return value "sink" is not actually an instance of SinglePETSink (which > has been defined as a local Python

Re: [lttng-dev] babletrace2 graph performance considerations

On 2020-03-30 1:30 p.m., Rocky Dunlap wrote: > In my case I have CTF trace where some analyses can be performed on a > per-stream basis (no need to mux the streams together).  In this case, I was > thinking that it would make sense to thread over the streams.  However, I > think can easily do th

Re: [lttng-dev] babletrace2 graph performance considerations

On 2020-03-30 6:34 p.m., Rocky Dunlap via lttng-dev wrote: > Each graph would parse the whole stream?  What if I only connect one of the > outputs from the source.ctf.fs?  I would think it would only access that one > stream file. Hmm yeah perhaps, I didn't think of that. Give it a try! Simon

Re: [lttng-dev] Babeltrace2 sink.ctf.fs creating many subdirectories

On 2020-04-03 8:50 a.m., Muresan, Heman via lttng-dev wrote: > Hi, > >   > > I’m using bt2 to combine multiple archives and I’m noticing some weird > behavior. Not sure if its something on my end. > >   > > I have a bunch of ctf trace archives and I am trying to combine them into one > ctf tr

Re: [lttng-dev] Babeltrace trimmer segfaults on custom trace

On 2021-05-04 10:21 a.m., Dimitri Scheftelowitsch via lttng-dev wrote: > > Hi, > > as mentioned on the IRC channel, babeltrace2 (both HEAD and current release > in the lttng Ubuntu 20 repo) aborts with a violated precondition in > `bt_clock_snapshot_get_ns_from_origin` on some custom traces we

Re: [lttng-dev] Babeltrace trimmer segfaults on custom trace

On 2021-05-04 9:57 p.m., Simon Marchi via lttng-dev wrote: > I tried to see if it would be possible for you > to just not use packets, but unfortunately I stumbled on what looks like > a bug in the CTF metadata parser, it hardcodes whether streams classes > have packets to true: >

Re: [lttng-dev] Transfer of LTTng copyright ownership: Simon Marchi

On 2022-01-14 2:39 p.m., Mathieu Desnoyers wrote: > Hi Simon, > > In order to facilitate maintenance of the LTTng project, would you agree to > transfer your copyright ownership for code authored outside of your employment > at EfficiOS to EfficiOS Inc. ? > > This particularly affects the lttng-t

Re: [lttng-dev] [PATCH lttng-tools] Copyright ownership transfer

On 2022-01-14 3:48 p.m., Jérémie Galarneau via lttng-dev wrote: > Apply copyright ownership transfer from David Goulet, Julien Desfossez, > and Simon Marchi to EfficiOS Inc. > > Link: https://lists.lttng.org/pipermail/lttng-dev/2022-January/030087.html > Link: https://lists.lttng.org/pipermail/ltt

Re: [lttng-dev] C API message iterator example for libbabeltrace2

On 8/12/22 09:19, Maksim Khmelevskiy via lttng-dev wrote: > Hi, > > there is a nice py message iterator example > but for C > API only plugins are covered with examples, do you think it would make > sense to create an example of a standal

Re: [lttng-dev] C API message iterator example for libbabeltrace2

On 8/20/22 12:14, Maksim Khmelevskiy via lttng-dev wrote: > Hi Simon, > thanks for the reply! > What I came up with for now is this example > . > It's probably has a lot of design mistakes but it's at least runnab

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

On 10/24/23 11:52, Seidl, Aron via lttng-dev wrote: > Hello guys, > I’m currently a student at the company Carl Zeiss in Oberkochen Germany. I’d > like to trace the Kernel from our CMM-Controller with CTF and convert it to > plain text, like Babeltrace 2 does. To understand how Babeltrace 2 works

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

On 10/25/23 03:29, 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) Don't do that (try to debug the binary in .libs directly). > I don't think I've ever i

Re: [lttng-dev] [babeltrace2]about python self-defined plugin loading

On 2024-04-26 09:56, Wu, Yannan via lttng-dev wrote: > Hihi, Kienan, > > I finally find a workaround. I could success with the following code: > file_name = "bt_plugin_latency_filter.py" > current_directory=os.getcwd() > > file_path = os.path.join(current_directory, file_name) > pset=bt2.find_