From: jamieexplorer@gmail.com (jamie explorer)
Subject: [lttng-dev] application changes to support lttng
Date: Tue, 30 Jun 2015 17:08:01 -0700 [thread overview]
Message-ID: <CACh_V578QYMi8CvhmvtR+QOY33maFNB6SB-eHBVOGOoJgUZ3HA@mail.gmail.com> (raw)
In-Reply-To: <CACh_V54iounQNr+jxP85YjPuivjMTgowOCuTaox9fMRC9=ty0w@mail.gmail.com>
Hi lttng-dev,
sorry for asking basic questions.
Can you guys point me to any documentation which has this info. lttng.org
documentation doesnt have info about this.
How does the app register to use lttng?
how do sessiond, app and lttng-ust interact? is there any socket from every
app to sessiond?
How is the app modified when instrumented using lttng? are there any
threads added?
Are there any powerful tools for analysis on collected traces.
/Jam
On Mon, Jun 29, 2015 at 10:03 AM, jamie explorer <jamieexplorer at gmail.com>
wrote:
> Hello,
>
> I have just started using lttng and still looking at documentation.
> Can you help me with some info.
>
> How does the app register to use lttng?
> how do sessiond, app and lttng-ust interact? is there any socket from
> every app to sessiond?
> How is the app modified when instrumented using lttng? are there any
> threads added?
> when lttng instrumentation is linked along with app
> Are there any powerful tools for analysis on collected traces.
>
> /Jam
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20150630/caf9b726/attachment.html>
prev parent reply other threads:[~2015-07-01 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 17:03 jamie explorer
2015-07-01 0:08 ` jamie explorer [this message]
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=CACh_V578QYMi8CvhmvtR+QOY33maFNB6SB-eHBVOGOoJgUZ3HA@mail.gmail.com \
--to=jamieexplorer@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