From: bedard.christophe@gmail.com (Christophe Bédard)
Subject: [lttng-dev] Correctly using callstack-user context
Date: Wed, 13 May 2020 11:34:55 -0400 [thread overview]
Message-ID: <CAAS9dobBZRWw3WkZQrn2UGkHC1+tuS0BLmZCJxpxSQvDjG7oxg@mail.gmail.com> (raw)
In-Reply-To: <bdeb584b-7c42-9e26-ce10-a1b008212541@versatic.net>
On Wed, 13 May 2020 at 10:18, Genevieve Bastien via lttng-dev <
lttng-dev at lists.lttng.org> wrote:
> We had a very very experimental branch with it, using backtrace first,
> then unwind. But it is not suggested, not performant. It's far from the
> correct desired implementation, for which Mathieu could give more details.
>
> It works, but not to be used in production. Students have used it in the
> lab for some specific use case prototyping. I won't share the branch here,
> but if you wish to try, let me know.
>
> Genevi?ve
>
Sure, I'd be interested!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20200513/75360007/attachment.htm>
parent reply other threads:[~2020-05-13 15:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bdeb584b-7c42-9e26-ce10-a1b008212541@versatic.net>]
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=CAAS9dobBZRWw3WkZQrn2UGkHC1+tuS0BLmZCJxpxSQvDjG7oxg@mail.gmail.com \
--to=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