From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: Brian Hutchinson <b.hutchman@gmail.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] Trying to understand use of lttng enable-event --kernel --userspace-probe=
Date: Thu, 18 May 2023 15:16:45 -0400 [thread overview]
Message-ID: <ce391c2f-4aae-413f-bcf3-4f3356499f34@efficios.com> (raw)
In-Reply-To: <CAFZh4h-aD==niaWF9Y=Z=bNm7vsUCWfaxkTBXAewyFXWVndCTg@mail.gmail.com>
On 2023-05-18 15:07, Brian Hutchinson wrote:
[...]
>>
>> If you attach to an ELF symbol (function), then there is no USDT in
>> play, so it should not be related to the issue you have.
>
> That is what I was thinking which is why I wanted to try it.
>
>>
>> But if your functions happen to be inlined, then there will be nothing
>> to attach to. Perhaps this is what happens there ?
>
> I don't see any evidence of anything being inlined in this module. I
> grepped the code to verify.
>
> Back to being stumped/stuck.
Make sure to check the resulting assembler and ELF symbol tables.
The compiler is free to inline various functions unless they are
explicitly marked as __attribute__((noinline)). Also, if LTO is enabled,
further optimization can be done at link-time.
One purpose of the UST tracepoints is to be less fragile with respect to
specific optimizations done by the compiler and linker, thus
guaranteeing that whatever is instrumented with a tracepoint is indeed
available for tracing.
Also, double-check that the path you pass to --userspace-probe really
targets your executable or .so binary file, and is not just a symbolic link.
Thanks,
Mathieu
--
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-18 19:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 2:11 Brian Hutchinson via lttng-dev
2023-05-17 16:08 ` Mathieu Desnoyers via lttng-dev
2023-05-17 16:37 ` Brian Hutchinson via lttng-dev
2023-05-17 17:17 ` Mathieu Desnoyers via lttng-dev
2023-05-18 13:17 ` Brian Hutchinson via lttng-dev
2023-05-18 14:10 ` Brian Hutchinson via lttng-dev
2023-05-18 14:46 ` Mathieu Desnoyers via lttng-dev
2023-05-18 15:00 ` Brian Hutchinson via lttng-dev
2023-05-18 18:58 ` Brian Hutchinson via lttng-dev
2023-05-18 19:03 ` Mathieu Desnoyers via lttng-dev
2023-05-18 19:07 ` Brian Hutchinson via lttng-dev
2023-05-18 19:16 ` Mathieu Desnoyers via lttng-dev [this message]
2023-05-18 19:28 ` Brian Hutchinson via lttng-dev
2023-05-18 19:20 ` Brian Hutchinson via lttng-dev
2023-05-18 19:24 ` Mathieu Desnoyers via lttng-dev
2023-05-18 19:32 ` 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=ce391c2f-4aae-413f-bcf3-4f3356499f34@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