From: Jonathan Rajotte-Julien via lttng-dev <lttng-dev@lists.lttng.org>
To: PFLANZER Moritz <moritz.pflanzer@hexagon.com>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Help needed: No UST events recorded
Date: Mon, 3 Aug 2020 11:31:55 -0400 [thread overview]
Message-ID: <20200803153155.GA207972@joraj-alpa> (raw)
In-Reply-To: <AM0PR06MB40030B857FF08F8B7685563FE64D0@AM0PR06MB4003.eurprd06.prod.outlook.com>
Hi Moritz
What is your version of lttng-tools?
lttng --version
Please run the `hello` executable using the LTTNG_UST_DEBUG env variable, while
tracing, and provide the output.
pkill lttng-sessiond
lttng-sessiond -b -vvv --verbose-consumer 2> /tmp/lttng-sessiond.log
lttng create
lttng enable-event -u -a
lttng start
LTTNG_UST_DEBUG=y ./hello
lttng stop
lttng destroy
pkill lttng-sessiond
Please also provide the /tmp/lttng-sessiond.log file via pastebin.
I suspect that if you cross-compiled lttng-ust from the master branch that
lttng-tools is not using the same version, resulting in the application not
being able to register to the lttng-sessiond.
Cheers
On Mon, Aug 03, 2020 at 09:35:25AM +0000, PFLANZER Moritz via lttng-dev wrote:
> Hi all!
>
> I'm struggling to get userspace tracing working on an aarch64 platform (busybox on top of Linux 5.4.24 kernel). I followed the guidelines in the docs and am currently using this example program for testing: https://github.com/lttng/lttng-ust/tree/master/doc/examples/hello-static-lib
> I cross-compiled lttng-ust and that example, but when I run the following commands on the platform no traces are recorded. If I use the same example on my x86 machine everything works as expected. (And kernelspace tracing is working on that aarch64 system.)
>
> Any hints where I could start investigating the issue are welcome.
>
> Regards,
> Moritz
>
> ~ # pwd
> /root
> ~ # lttng create
> Spawning a session daemon
> Session auto-20200720-174509 created.
> Traces will be written in /root/lttng-traces/auto-20200720-174509
> ~ # lttng enable-event -au
> All UST events are enabled in channel channel0
> ~ # lttng start
> Tracing started for session auto-20200720-174509
> ~ # ./hello
> Hello, World!
> Tracing... done.
> ~ # lttng destroy
> Session auto-20200720-174509 destroyed
> ~ # ll
> total 40
> -rwxr-xr-x 1 root root 39280 Jul 20 17:44 hello*
>
>
>
> Moritz Pflanzer
> Software Development Engineer
>
> [cid:image001.png@01D3BF6E.185110B0]
>
> Räffelstrasse 28
>
> 8045 Zürich
> E: moritz.pflanzer@hexagon.com<mailto:moritz.pflanzer@hexagon.com><mailto:carolin.siebert@hexagon.com>
> W: http://www.hexagongeosystems.com
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Jonathan Rajotte-Julien
EfficiOS
_______________________________________________
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:[~2020-08-03 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 9:35 [lttng-dev] Help needed: No UST events recorded PFLANZER Moritz via lttng-dev
2020-08-03 15:31 ` Jonathan Rajotte-Julien via lttng-dev [this message]
2020-08-04 8:15 ` PFLANZER Moritz via lttng-dev
2020-08-04 13:09 ` Jonathan Rajotte-Julien via lttng-dev
2020-08-05 4:50 ` PFLANZER Moritz 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=20200803153155.GA207972@joraj-alpa \
--to=lttng-dev@lists.lttng.org \
--cc=jonathan.rajotte-julien@efficios.com \
--cc=moritz.pflanzer@hexagon.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;
as well as URLs for NNTP newsgroup(s).