From: Alexander Krabler via lttng-dev <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] Record stacktraces at userspace tracing domain
Date: Mon, 2 Dec 2024 16:29:45 +0000 [thread overview]
Message-ID: <VI1PR01MB6845D1C81221547CEC94B3A782352@VI1PR01MB6845.eurprd01.prod.exchangelabs.com> (raw)
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
next reply other threads:[~2024-12-02 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 16:29 Alexander Krabler via lttng-dev [this message]
2024-12-02 21:17 ` Christophe Bédard via lttng-dev
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=VI1PR01MB6845D1C81221547CEC94B3A782352@VI1PR01MB6845.eurprd01.prod.exchangelabs.com \
--to=lttng-dev@lists.lttng.org \
--cc=Alexander.Krabler@kuka.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