Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: "MOESSBAUER, Felix via lttng-dev" <lttng-dev@lists.lttng.org>
To: "MOESSBAUER, Felix via lttng-dev" <lttng-dev@lists.lttng.org>
Subject: babeltrace master: trace-compass is unable to open trace with index
Date: Wed, 5 Aug 2026 10:16:33 +0000	[thread overview]
Message-ID: <5eed80a93b79f22f7c30a383f2a7b4d6f7068a97.camel@siemens.com> (raw)

Hi,

the babeltrace version from the master branch (65fb4669f) is able to
create LTTng index files. However, these index files seem to be
incompatible with trace-compass.

On loading such a trace, trace-compass (incubator version, 0.18.0-
20260711-0558, or release 12.0.0) issues the following error message:

> Error initializing trace.
> org.eclipse.tracecompass.tmf.core.exceptions.TmfTraceException:
> Failed to allocate mapped byte buffer at 36 of size 416 on a
> file of size 176

I double checked the traces with babeltrace and
https://github.com/eepp/jacquesctf , which are both able to properly
read the traces.

For reproducing, run the
tests/plugins/sink.ctf.fs/test_create_lttng_index.py test and open any
of the generated CTF files in trace-compass. I explicitly tested and
reproduced it with "with-packets-ctf-2" and "no-packets-ctf-2".

The traces itself are valid, which can be proved by removing the index
file and successfully re-opening them in trace-compass.

PS: I'm pretty sure this is a trace-compass bug, but as I'm not a
member of the tracecompass-dev ML, I report it here. Feel free to
forward.

Best regards,
Felix Moessbauer

-- 
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany


             reply	other threads:[~2026-08-05 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 10:16 MOESSBAUER, Felix via lttng-dev [this message]
2026-08-05 14:10 ` Arnaud Fiorini via lttng-dev

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=5eed80a93b79f22f7c30a383f2a7b4d6f7068a97.camel@siemens.com \
    --to=lttng-dev@lists.lttng.org \
    --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