From: "Christophe Bédard via lttng-dev" <lttng-dev@lists.lttng.org>
To: Alexander Krabler <Alexander.Krabler@kuka.com>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Record stacktraces at userspace tracing domain
Date: Mon, 2 Dec 2024 13:17:17 -0800 [thread overview]
Message-ID: <CAAS9dobC0wERGMQf9CLjhYY4ay_zSdAMAE9qxBezLtH-kL_1NQ@mail.gmail.com> (raw)
In-Reply-To: <VI1PR01MB6845D1C81221547CEC94B3A782352@VI1PR01MB6845.eurprd01.prod.exchangelabs.com>
[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]
Hi,
I did the same thing a while ago, i.e., trigger tracepoints on
malloc/free/etc. using liblttng-ust-libc-wrapper and collect userspace
callstack information (so that the indirect calls to malloc/free can be
removed from an application).
There is a userspace callstack context implementation here for lttng-ust
2.10, see the last 3 commits:
https://github.com/tahini/lttng-ust-1/commits/ust-callstack-2.10/. Here's
the corresponding lttng-tools 2.10 branch needed to enable the userspace
callstack context:
https://github.com/tahini/lttng-tools/commits/ust-context-callstack/.
I've rebased it on 2.11 here:
https://github.com/ApexAI/lttng-ust/commits/ust-callstack-2.11/.
lttng-tools:
https://github.com/ApexAI/lttng-tools/commits/ust-callstack-2.11/. It
shouldn't be too hard to rebase it all on a newer version.
Hope that helps,
Christophe
On Mon, Dec 2, 2024 at 8:32 AM Alexander Krabler via lttng-dev <
lttng-dev@lists.lttng.org> wrote:
> Hello,
>
> we want to record stacktraces at specific userspace events like e.g. calls
> to malloc and free using liblttng-ust-libc-wrapper.so.
> There is the callstack-user context to achieve this in general, however,
> it seems like tracing of userspace stacktraces is only available in the
> kernel tracing domain.
>
> Is there already a solution to achieve this goal?
> If not, what would need to be done to achieve this?
>
> Thanks,
> Alexander
[-- Attachment #2: Type: text/html, Size: 2190 bytes --]
next prev parent reply other threads:[~2024-12-02 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 16:29 Alexander Krabler via lttng-dev
2024-12-02 21:17 ` Christophe Bédard via lttng-dev [this message]
2024-12-10 16:41 ` Kienan Stewart via lttng-dev
2024-12-11 10:32 ` AW: " Alexander Krabler via lttng-dev
2024-12-11 15:43 ` Mathieu Desnoyers via lttng-dev
2024-12-12 16:52 ` Alexander Krabler via lttng-dev
2024-12-12 16:56 ` Dirk Eibach 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=CAAS9dobC0wERGMQf9CLjhYY4ay_zSdAMAE9qxBezLtH-kL_1NQ@mail.gmail.com \
--to=lttng-dev@lists.lttng.org \
--cc=Alexander.Krabler@kuka.com \
--cc=bedard.christophe@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