Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: David Aldrich via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: Function tracing not working
Date: Mon, 2 Jun 2025 15:37:30 +0100	[thread overview]
Message-ID: <CAJK_ieigCAaowdcwmLbkdL1J3eFgHE7t1W=ZKRvoKhgABM46yw@mail.gmail.com> (raw)

Hi,

I am trying to use lttng-ust-cyg-profile.

Our application is large so, so far, I only compile main.cpp with
compiler option '-finstrument-functions' (I don't specify option
'-pg').

Our app must be run as root so I run it, and capture with lttng, like this:

lttng create app_trace
lttng enable-event --userspace 'lttng_ust_tracef:*'
lttng enable-channel --kernel --session app_trace kernel_channel
lttng enable-event --kernel --all --channel kernel_channel --session app_trace
export LD_PRELOAD=liblttng-ust-cyg-profile.so
lttng start
sudo -E ./myapp
lttng stop

I notice that many events get discarded:

Warning: 198522 events were discarded, please refer to the
documentation on channel configuration.

I then import into TraceCompass.  I see the traces in the Resources
View, but when I expand Experiment > Views, all 3 'LTTng-UST
CallStack' entries are striked through so I can't select them. So I
can't visualise the function calls.

Any idea what I am doing wrong please?

Best regards, David

             reply	other threads:[~2025-06-02 14:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02 14:37 David Aldrich via lttng-dev [this message]
2025-06-02 17:22 ` Mathieu Desnoyers via lttng-dev
2025-06-04 16:22   ` David Aldrich via lttng-dev
2025-06-05 10:49     ` David Aldrich via lttng-dev
2025-06-05 18:49       ` Mathieu Desnoyers via lttng-dev
2025-06-06 14:37         ` David Aldrich via lttng-dev
2025-06-06 18:14           ` Mathieu Desnoyers 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='CAJK_ieigCAaowdcwmLbkdL1J3eFgHE7t1W=ZKRvoKhgABM46yw@mail.gmail.com' \
    --to=lttng-dev@lists.lttng.org \
    --cc=david.aldrich.ntml@gmail.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