Re: Malformed Tracefiles

[Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>]

Hi Georg,

a good first step is to run lttng-session with `-vvv --verbose-consumer` 
and inspect the log file and `LTTNG_UST_DEBUG=1` in the environment.

It may also be useful to run your traced applications with 
`LTTNG_UST_DEBUG=1` set in the environment.

Do you have steps that reproduce the issue? E.g., all the commands to 
set up the tracing session and so forth.

thanks,
kienan

On 6/19/25 10:58 AM, Georg Muck via lttng-dev wrote:
> Hey,
> 
> I am using the LTTng tracer (2.13.11, C-API, rotation=1s) to trace my ROS2
> system (userspace only). Everything works just fine within my Docker
> Container (Ubuntu 24.04), but if I start the same procedure on the host
> itself (also Ubuntu 24.04), it does not create a TraceFile if to many
> tracepoints occur (speaking of roundabout 1500+ per second) (sometimes it
> malformed the tracefile, but I was not able to recreate that. If I remember
> correctly, Babeltrace2 threw an error that said that there was no
> metadata-file). I played around with some configurations (like increasing
> the buffer size from ~16kB to ~512kB or a less aggressive rotation), but
> the problem stayed.
> 
> Would be thankful for help. I guess I delivered to less information, please
> reach out what is interesting at this point, I am not sure about that :).
> 
> Best regards,
> Georg
> 
> 
> 
> Never burn the bridges before you
> If you've burned the bridges behind
> Never burn the one that you're walking upon
> Or you're sure to hit the water in time. *(Savatage, Streets, 1991)*
>