Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: David Aldrich <david.aldrich.ntml@gmail.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: Function tracing not working
Date: Fri, 6 Jun 2025 14:14:25 -0400	[thread overview]
Message-ID: <9fb7448a-9537-4014-bcd8-40e6dbff58a2@efficios.com> (raw)
In-Reply-To: <CAJK_iehv1BWCp5FOfXkrDpPoDTG1nnhAZ4iCS1rRwjQbpQQkxQ@mail.gmail.com>

On 2025-06-06 10:37, David Aldrich wrote:
> Hi Mathieu
> 
>> Indeed, You will also need to enable something like this:
>>
>> lttng enable-event --userspace 'lttng_ust_cyg_profile:*'
>>
>> See "man 3 lttng-ust-cyg-profile" for details.
> 
> Thanks for this. I used your suggested command and can now see the
> Flame Chart (Incubator). However, I only see symbol addresses, not the
> actual symbolic names.
> 
> I compile with:
> 
> -O3 -pg -finstrument-functions
> 
> Do I need any other compiler/linker options to resolve the symbol names?

Yes. Resolving addresses to symbol names requires to know the
base addresses where the executable mappings are loaded.

See:

man 7 babeltrace2-filter.lttng-utils.debug-info

for a detailed explanation about what needs to be enabled.

Thanks,

Mathieu


> 
> Best regards
> David


-- 
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02 14:37 David Aldrich via lttng-dev
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 [this message]

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=9fb7448a-9537-4014-bcd8-40e6dbff58a2@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=david.aldrich.ntml@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