From: Philippe Proulx via lttng-dev <lttng-dev@lists.lttng.org>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
Cc: "MOESSBAUER, Felix via lttng-dev" <lttng-dev@lists.lttng.org>
Subject: Re: babeltrace 2.1.2: sink.ctf.fs does not deduplicate identical clocks
Date: Thu, 6 Aug 2026 14:45:53 -0400 [thread overview]
Message-ID: <CAB4xu_3zXGL4a20TRK2m2OwfC7NPqVW6tJvM397er0w6dBwSLw@mail.gmail.com> (raw)
In-Reply-To: <d0e142586819e25725452b2849308829c38216fb.camel@siemens.com>
On Tue, Aug 4, 2026 at 11:28 AM MOESSBAUER, Felix via lttng-dev
<lttng-dev@lists.lttng.org> wrote:
>
> Hi,
>
> while porting the bt2-ftrace-to-ctf [1] plugin to babeltrace 2.1, I
> noticed that the sink.ctf.fs creates invalid clock definitions if
> multiple stream-classes share the same clock-class. In this case, the
> clock definition is added multiple times to the CTF 2 metadata,
> resulting in the following assertion on read-back:
>
> ERROR: [Babeltrace CLI] (babeltrace2.c:2705)
> Command-line error: retcode=1
> CAUSED BY [Source auto-discovery] (autodisc/autodisc.c:493)
> babeltrace.support-info query failed.
> CAUSED BY [libbabeltrace2] (lib/graph/query-executor.c:233)
> Component class's "query" method failed: query-exec-
> addr=0x55cba00c12e0, cc-addr=0x55cba00b4100, cc-type=SOURCE, cc-
> name="fs", cc-partial-descr="Read CTF traces from
> the file sy", cc-is-frozen=0, cc-so-handle-addr=0x55cba00b1930, cc-
> so-handle-path="<...>/build/babeltrace-plugin-ctf.so",
> object="babeltrace.support-info", params-addr=0x55cba00cd470, params-
> type=MAP, params-element-count=2, log-level=WARNING
> CAUSED BY ['source.ctf.fs'] (plugins/ctf/common/src/metadata/json/ctf-
> 2-metadata-stream-parser.cpp:130)
> [1:1 @ 8512 bytes] Invalid fragment #12.
> CAUSED BY ['source.ctf.fs'] (plugins/ctf/common/src/metadata/json/ctf-
> 2-metadata-stream-parser.cpp:367)
> [1:1 @ 17024 bytes] Duplicate clock class fragment with ID `local`.
See <https://review.lttng.org/c/babeltrace/+/18460>.
Let's continue the discussion on Gerrit if need be.
Thank you for the report and reproducer.
Philippe
>
> When running with MIP=0, the CTF 1.8 data does not have this issue (or
> the reader ignores the duplicated definitions).
>
> [1] https://github.com/siemens/bt2-ftrace-to-ctf
>
> Attached you will find an AI generated reproducer using just the
> babeltrace2 Python bindings.
>
> Best regards,
> Felix Moessbauer
>
> --
> Siemens AG
> Linux Expert Center
> Friedrich-Ludwig-Bauer-Str. 3
> 85748 Garching, Germany
>
prev parent reply other threads:[~2026-08-06 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 15:27 MOESSBAUER, Felix via lttng-dev
2026-08-06 18:45 ` Philippe Proulx via lttng-dev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAB4xu_3zXGL4a20TRK2m2OwfC7NPqVW6tJvM397er0w6dBwSLw@mail.gmail.com \
--to=lttng-dev@lists.lttng.org \
--cc=eeppeliteloop@gmail.com \
--cc=felix.moessbauer@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox