Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Jonathan Rajotte-Julien via lttng-dev <lttng-dev@lists.lttng.org>
To: MONTET Julien <julien.montet@reseau.eseo.fr>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Issues on basic LTTng trace userspace (tutorial)
Date: Wed, 24 Mar 2021 10:25:40 -0400	[thread overview]
Message-ID: <20210324142540.GB344120@joraj-alpa> (raw)
In-Reply-To: <PR3PR02MB62023431654FB93182EA21A1D1639@PR3PR02MB6202.eurprd02.prod.outlook.com>

Hi Julien,

On Wed, Mar 24, 2021 at 11:29:04AM +0000, MONTET Julien via lttng-dev wrote:
> Hello the LTTng team !
> 
> I would like, at first, to thank you for your projet and your impressive work !
> 
> For the past few days I have been trying to learn how to use lttng (v2.12).
> 
> I followed the installation on your website for an Ubuntu 20.04.
> [cid:c663399f-0584-43d3-90c5-3aa277ee7020]

Good. So just to validate you used the stable 2.12 PPA as described in this
section [1] ?.

[1] https://lttng.org/docs/v2.12/#doc-ubuntu-ppa

> 
> The steps to get the trace of a Linux kernel and the babel trace are great !
> 
> However, I am stuck for the 'Trace a user application' : https://lttng.org/docs/v2.12/#doc-tracing-your-own-user-application
> Compilation steps are ok, it launches without error but lttng list --userspace  gives me nothing.

When you perform the `lttng list --userspace` command is your user application
running? If not, `lttng list --userspace` can only list running application.

If your application is running, we will need to go a bit further and have some
debug info.

You can at least check if lttng-ust, on the application side, can successfully
communicate with the lttng-sessiond process. For this, you will have to use
LTTNG_UST_DEBUG.

Here's how to us it:

 1) Make sure a lttng-sessiond is present,
 2) Start your application like so:  LTTNG_UST_DEBUG=1 your_application,
 3) Debug messages from lttng-ust should appear on the stderr.

Please use a paste service [2] to share this information with us. 

[2] https://paste.ubuntu.com/

Au plaisir!

-- 
Jonathan Rajotte-Julien
EfficiOS
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  reply	other threads:[~2021-03-24 14:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24 11:29 MONTET Julien via lttng-dev
2021-03-24 14:25 ` Jonathan Rajotte-Julien via lttng-dev [this message]
     [not found]   ` <PR3PR02MB6202F969540C279A6A171F83D1639@PR3PR02MB6202.eurprd02.prod.outlook.com>
2021-03-24 15:32     ` Jonathan Rajotte-Julien via lttng-dev
2021-03-24 15:53       ` MONTET Julien via lttng-dev
2021-03-24 16:06         ` Jonathan Rajotte-Julien via lttng-dev
2021-03-24 16:36           ` Jonathan Rajotte-Julien via lttng-dev
2021-03-24 18:55             ` MONTET Julien via lttng-dev
2021-03-24 19:00               ` Jonathan Rajotte-Julien via lttng-dev
2021-03-24 19:08                 ` MONTET Julien 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=20210324142540.GB344120@joraj-alpa \
    --to=lttng-dev@lists.lttng.org \
    --cc=jonathan.rajotte-julien@efficios.com \
    --cc=julien.montet@reseau.eseo.fr \
    /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