From: milian.wolff@kdab.com (Milian Wolff)
Subject: [lttng-dev] LTTng user-space callstacks
Date: Thu, 26 Mar 2020 21:52:57 +0100 [thread overview]
Message-ID: <1834419.usQuhbGJ8B@agathebauer> (raw)
In-Reply-To: <2022773652.13655.1585251677207.JavaMail.zimbra@efficios.com>
On Donnerstag, 26. M?rz 2020 20:41:17 CET Mathieu Desnoyers via lttng-dev
wrote:
> ----- On Mar 26, 2020, at 1:39 PM, lttng-dev <lttng-dev at lists.lttng.org>
wrote:
> > Hello!
> >
> > Currently, callstack collection in LTTng is only available for
> > kernel-space
> > events with context fields callstack-kernel and callstack-user .
> >
> > Is it expected that callstack collection for LTTng-UST will be added too?
> > And if it is expected, then how soon?
>
> Hi Valentin,
>
> It is something that would be interesting and useful, but a lot of work
> would be needed to have stack-walking this is fast enough and reentrant wrt
> signal handlers. Unfortunately, the backtrace(3) functions do not meet
> those requirements.
>
> Also, for gathering user-space callstacks from the kernel tracer, it only
> works if all user-space is compiled with frame pointers. This is also a
> limitation that would require a lot of work to overcome neatly.
>
> None of those features are currently on any roadmap due to lack of customers
> showing interest in getting this done.
libunwind [1] should meet the requirements you need. It is high performance
thanks to extensive caching, signal safe and does not rely on frame pointers.
[1]: https://github.com/libunwind/libunwind
--
Milian Wolff | milian.wolff at kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL Experts
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3826 bytes
Desc: not available
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20200326/9c3b8cf4/attachment.bin>
next prev parent reply other threads:[~2020-03-26 20:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 17:39 Valentin Grigorev
2020-03-26 19:41 ` Mathieu Desnoyers
2020-03-26 20:52 ` Milian Wolff [this message]
2020-03-27 13:44 ` Valentin Grigorev
2020-03-27 13:55 ` Mathieu Desnoyers
2020-03-27 15:05 ` Valentin Grigorev
2020-03-27 17:18 ` Milian Wolff
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=1834419.usQuhbGJ8B@agathebauer \
--to=milian.wolff@kdab.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