From: Zheng.Chang@emc.com (Zheng.Chang@emc.com)
Subject: [lttng-dev] Some questions about Lttng
Date: Mon, 18 Jun 2012 23:50:04 -0400 [thread overview]
Message-ID: <6539770C71C3814BB0BFC2DBEBD105087948C2@CORPUSMX30B.corp.emc.com> (raw)
Hi folks,
I'm studying how to use Lttng now. I built a kernel which version is
2.6.38 and ran with lttng 2.0.
I got some confused when I started to use it. Here are my questions:
1. I didn't see kernel patches for kernel 3.x. Does it mean kernel 3.x
support it already?
2. I tried to do something like, dump the arguments of system call, or
dump a backtrace in a specified function. But the output of lttng is
very limited. Is there a way to do that with lttng?
3. I looked into some UST examples and found here are three header
files: tracepoint.h, tracepoint-event.h and ust-tracepoint-event.h.
They have some duplicated macro definitions like TRACEPOINT_EVENT.
And the examples includes all of these three header files despite no
conflict here. Could someone help to explain the intention?
4. Once I defined a tracepoint in my code, seems some initializations
would register default probe into the hook point. How to disable the
default probe and register my self-defined probes?
5. Does lttng-ust support dynamic traceing like kprobe?
I'm a newbie of lttng. Any help will be appreciated.
Thanks
Zheng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20120618/fc0aab1f/attachment.html>
next reply other threads:[~2012-06-19 3:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 3:50 Zheng.Chang [this message]
2012-06-19 9:28 ` Francis Giraldeau
2012-06-19 16:36 ` Mathieu Desnoyers
2012-06-20 5:30 ` Zheng.Chang
2012-06-20 13:03 ` Mathieu Desnoyers
2012-06-21 4:59 ` Zheng.Chang
2012-06-21 12:45 ` Mathieu Desnoyers
2012-06-25 7:32 ` changz
2012-06-26 6:06 ` Mathieu Desnoyers
2012-06-26 8:59 ` changz
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=6539770C71C3814BB0BFC2DBEBD105087948C2@CORPUSMX30B.corp.emc.com \
--to=zheng.chang@emc.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