archive mirror
 help / color / mirror / Atom feed
From: Mathieu Desnoyers via lttng-dev <>
To: Valentin Grigorev <>
Cc: lttng-dev <>
Subject: Re: LTTng user-space callstacks
Date: Thu, 26 Mar 2020 15:41:17 -0400 (EDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1.1: Type: text/plain, Size: 1030 bytes --]

----- On Mar 26, 2020, at 1:39 PM, lttng-dev <> 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 

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. 



Mathieu Desnoyers 
EfficiOS Inc. 

[-- Attachment #1.2: Type: text/html, Size: 1917 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

lttng-dev mailing list

  reply	other threads:[~2020-03-26 19:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 17:39 Valentin Grigorev via lttng-dev
2020-03-26 19:41 ` Mathieu Desnoyers via lttng-dev [this message]
2020-03-26 20:52   ` Milian Wolff via lttng-dev
2020-03-27 13:44     ` Valentin Grigorev via lttng-dev
2020-03-27 13:55       ` Mathieu Desnoyers via lttng-dev
2020-03-27 15:05         ` Valentin Grigorev via lttng-dev
2020-03-27 17:18         ` Milian Wolff 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: LTTng user-space callstacks' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).