From: "MOESSBAUER, Felix via lttng-dev" <lttng-dev@lists.lttng.org>
To: "eeppeliteloop@gmail.com" <eeppeliteloop@gmail.com>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"Poljakow, Andre" <andre.poljakow@siemens.com>
Subject: Re: babeltrace | sink.ctf.fs escaping of struct member names
Date: Thu, 4 Dec 2025 16:07:43 +0000 [thread overview]
Message-ID: <8eb94fdf35b763ed20b6470f737c55926cd0f0ca.camel@siemens.com> (raw)
In-Reply-To: <CAB4xu_3+ve5iusvBMPhN2cv9K7N-r4qwa92k4RrFT_WNMPqi4w@mail.gmail.com>
On Thu, 2025-12-04 at 11:01 -0500, Philippe Proulx wrote:
> On Thu, Dec 4, 2025 at 10:47 AM MOESSBAUER, Felix
> <felix.moessbauer@siemens.com> wrote:
> >
> > Well... This is a more generic question if it is really the job of the
> > serializer to fix possible name clashes in the output. Anyways,
> > unfortunately LTTng uses this field and does not allow escaping.
>
> Although I understand the question, I will not take the time to
> re-evaluate a design that involves CTF 1.8. I'm currently in a "quick
> fixes only" mode for this format, with the sole aim of keeping existing
> scenarios working.
>
> > I would love to switch to CTF2, however we need support for it in
> > trace-compass, which AFAIK is not even implemented yet.
>
> We're currently investigating the status of CTF 2 support in Trace
> Compass and what amount of work is remaining. We'll let you know.
>
> > This is tricky, as we don't really know if the trace is an LTTng trace
> > or not. However, we can hide it behind the proposed create-lttng-index
> > flag, as it is anyways only needed in combination with an index (I
> > still don't know why, but ok...).
>
> Yes we know. Have a look at make_lttng_trace_path_rel().
I already checked this function, but this is a bit too-strict, as
really only adding the index breaks the import. I also want to be able
to add the index to non lttng traces (which for instance lack some env
metadata) as otherwise the ftrace-to-ctf converter needs to fake the
metadata.
>
> `create-lttng-index` would be another hint, but the trace environment
> has been good enough so far.
This is easy to implement and works perfectly fine. By that, traces
without an lttng index have "_cpu_id" and can be imported in trace-
compass. Traces with an lttng index get "cpu_id" and also now import
correctly.
I hope this solution is acceptable.
Anyways, thanks for the quick support.
Felix
>
> Phil
--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
prev parent reply other threads:[~2025-12-04 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 10:10 MOESSBAUER, Felix via lttng-dev
2025-12-04 15:15 ` Philippe Proulx via lttng-dev
2025-12-04 15:47 ` MOESSBAUER, Felix via lttng-dev
2025-12-04 16:01 ` Philippe Proulx via lttng-dev
2025-12-04 16:07 ` MOESSBAUER, Felix 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=8eb94fdf35b763ed20b6470f737c55926cd0f0ca.camel@siemens.com \
--to=lttng-dev@lists.lttng.org \
--cc=andre.poljakow@siemens.com \
--cc=eeppeliteloop@gmail.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@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