[lttng-dev] I'm still getting empty ust traces using tracef

Mathieu Desnoyers mathieu.desnoyers at efficios.com
Fri May 12 09:34:23 EDT 2023

[adding back the mailing list]

On 2023-05-12 09:33, Mathieu Desnoyers wrote:
> On 2023-05-12 00:10, Brian Hutchinson wrote:
>> Hmm, I missed this earlier somehow.
>> So, I'm not the greatest at updating OE and Yocto recipes.  I'm
>> currently using this recipe:
>> http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-kernel/lttng/lttng-ust_2.13.5.bb?h=master
>> ... and it looks like the commit you are talking about is newer.
>> I always think, oh, I'll just update the source URI in the recipe but
>> it's never that simple ... and there are patches in the recipe etc.
>> I've got a sdk (external toolchain) built for my embedded platform.
>> Would it be too hard to just download stable-2.13 of everything and
>> cross compile it outside of Yocto?
>> What do you suggest?
>> And do I need to do anything besides just get 2.13 stable working?  I
>> was kind of confused if I need to put a #define
>> LTTNG_TRACEPOINT_DEFINE somewhere in my code.  I'm not using a
>> tracepoint provider packages at this point
> Hi Brian,
> You might want to provide a trimmed-down reproducer of your issue: 
> example .c compile unit instrumented with tracepoints, example .c 
> compile unit containing the tracepoint probes, and the log of the 
> console when this application is run with LTTNG_UST_DEBUG=1.

> Thanks,
> Mathieu

Mathieu Desnoyers
EfficiOS Inc.

More information about the lttng-dev mailing list