From: kirankumarp@uurmi.com (kirankumarp@uurmi.com)
Subject: [lttng-dev] C APIs tracing control
Date: Mon, 29 May 2017 06:32:35 +0000 [thread overview]
Message-ID: <4485def9e3e2e8b07f166e9fdbcdbe3a@cloudmailn6.netcore.co.in> (raw)
Hi,
we are developing an application and want to have LTTng control within it. We would like to know the C APIs for it.
we require following APIs following command line commands-
lttng create
lttng list
lttng enable-event
lttng start
lttng stop
lttng destroy
We could find some documentation at but not sure if we are right. Also it will be great help, if you can provide an makefile for this (to link the libraries and Paths to be included).
We tried "lttng_create_handle", "lttng_create_session" API (as mentioned in the documentation) but its not getting compiled.
Please help on this regard.
Thanks in advance.
Regards
Kiran Kumar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20170529/b64ec323/attachment.html>
next reply other threads:[~2017-05-29 6:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 6:32 kirankumarp [this message]
2017-05-29 15:40 ` Jonathan Rajotte-Julien
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=4485def9e3e2e8b07f166e9fdbcdbe3a@cloudmailn6.netcore.co.in \
--to=kirankumarp@uurmi.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