From: pierre-marc.fournier@polymtl.ca (Pierre-Marc Fournier)
Subject: [ltt-dev] Userspace LTTng code (UST)
Date: Wed, 6 Jan 2010 14:54:12 -0500 [thread overview]
Message-ID: <201001061454.12920.pierre-marc.fournier@polymtl.ca> (raw)
In-Reply-To: <827771.91399.qm@web112520.mail.gq1.yahoo.com>
On December 15, 2009 22:50:55 Poop Rabbit wrote:
> Hi,
Hi!
>
> I am trying to understand whether the LTTng user space project has reached
> a point of maturity such that user space tracing can be used with a user
> space application.? I have not seen any officially released packages or
> source.
>
> Can someone please elaborate on the state of the LTTng user space source
> code?? Where can I find an official release?? Will
> http://lists.casi.polymtl.ca/ to include more detailed information with
> regard to UST?
Indeed, no release has been done yet.
The code can be found here:
http://git.dorsal.polymtl.ca/?p=ust.git;a=summary
The tracer does work, with the following caveats:
- per-cpu buffers are not yet there (buffers are per-process)
- flight recorder is not yet functional
- in some cases, tracing does not persist across child process creation
A 0.1 release is targeted for this month.
pmf
parent reply other threads:[~2010-01-06 19:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <827771.91399.qm@web112520.mail.gq1.yahoo.com>]
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=201001061454.12920.pierre-marc.fournier@polymtl.ca \
--to=pierre-marc.fournier@polymtl.ca \
/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