From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: Brian Hutchinson <b.hutchman@gmail.com>, lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] I'm still getting empty ust traces using tracef
Date: Thu, 11 May 2023 14:13:00 -0400 [thread overview]
Message-ID: <41fa4914-b519-9ff9-3659-7e4cf2d41904@efficios.com> (raw)
In-Reply-To: <CAFZh4h8awEpJgAcygRY=1f7A2qK91b31HBnLBPvvueuRnquOjQ@mail.gmail.com>
On 2023-05-11 12:36, Brian Hutchinson via lttng-dev wrote:
> ... more background. I've always used ltt in the kernel so I don't
> have much experience with the user side of it and especially
> multi-threaded, multi-core so I'm probably missing some fundamental
> concepts that I need to understand.
Which are the exact versions of LTTng-UST and LTTng-Tools you are using
now ? (2.13.N or which git commit ?)
Thanks,
Mathieu
>
> Regards,
>
> Brian
>
> On Thu, May 11, 2023 at 11:53 AM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>
>> Hi,
>>
>> I posted a while ago (thread - Using lttng 2.11 and UST doesn't appear
>> to work - getting empty trace files) about this problem I'm having
>> with getting empty trace logs.
>>
>> I've since upgraded to lttng v2.13 and while I can do a simple hello
>> world program with tracef and get events in the log files, my more
>> complicated large multi-threaded app I'm trying to debug is still
>> getting empty log file traces.
>>
>> I can list the user space events in my app.
>>
>> Next I do:
>>
>> lttng enable-event --userspace 'lttng_ust_tracef:*'
>>
>> ... to enable the events, start lttng, start my app, .... and I get a
>> trace directory structure that's empty.
>>
>> I feel like I've read every thread in the archives about people having
>> the same problem.
>>
>> I did try using LD_PRELOAD with various libs thinking that was the
>> problem but so far I'm still getting empty traces.
>>
>> So far I've tried:
>>
>> LD_PRELOAD=liblttng-ust-libc-wrapper.so.1:liblttng-ust-pthread-wrapper.so.1:liblttng-ust-dl.so.1:liblttng-ust-fork.so.1:liblttng-ust-fd.so.1
>> /usr/local/bin/my_app
>>
>> I guess one question I have is how do I determine which "helper libs"
>> I need to preload?
>>
>> The application I'm working on is made up of a bunch of smaller static
>> libs linked together into one big executable and that is linked with
>> -llttng-ust and -ldl.
>>
>> I'm pretty stuck at the moment. Anyone have any wisdom on what I
>> might be doing wrong or how I can tell why I'm not getting events in
>> the logs?
>>
>> Thanks,
>>
>> Brian
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2023-05-11 18:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 15:53 Brian Hutchinson via lttng-dev
2023-05-11 16:36 ` Brian Hutchinson via lttng-dev
2023-05-11 18:13 ` Mathieu Desnoyers via lttng-dev [this message]
2023-05-11 18:15 ` Mathieu Desnoyers via lttng-dev
[not found] ` <CAFZh4h9M0eA1SpHhfquoyrqtwRhHV54f0O4hCkkiojwUmPTC9Q@mail.gmail.com>
[not found] ` <fdbcfbd9-742d-dc61-3667-48a00130d6aa@efficios.com>
2023-05-12 13:34 ` Mathieu Desnoyers via lttng-dev
2023-05-12 14:52 ` Brian Hutchinson via lttng-dev
2023-05-12 14:57 ` Mathieu Desnoyers via lttng-dev
2023-06-20 22:02 ` Brian Hutchinson via lttng-dev
2023-06-21 20:21 ` Mathieu Desnoyers via lttng-dev
2023-06-21 22:02 ` Brian Hutchinson via lttng-dev
2023-06-28 22:02 ` Brian Hutchinson via lttng-dev
2023-05-11 18:38 ` Brian Hutchinson via lttng-dev
2023-05-11 18:14 ` Michael Jeanson via lttng-dev
2023-05-11 18:42 ` Brian Hutchinson via lttng-dev
2023-05-11 18:57 ` Brian Hutchinson 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=41fa4914-b519-9ff9-3659-7e4cf2d41904@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=b.hutchman@gmail.com \
--cc=mathieu.desnoyers@efficios.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