Hi Sebastian,
In our company one of the main lttng applications is to measure latency
between two probes which get same ID as argument. For this purpose we've
implemented in C a special utility which is based on libraries to read CTF
(IIRC). Also some developers often use own simple perl scripts
--
Date: Fri, 17 Oct 2014 21:39:21 +
From: Boisvert, Sebastien boisv...@anl.gov
I wrote a big .tp file to define numerous tracepoints that only differ in the
event name.
They all take the same arguments and they all dump
Hi Shariyar,
Can your trace be read all right if you import it in TMF (Trace Compass)
and open it normally in it? Do all events appear in the events table?
There were changes to improve the CTF reading part recently and somebody
reported a bug with traces taken on ARM where events are not read
Are TRACEPOINT_EVENT_CLASS and
TRACEPOINT_EVENT_INSTANCE part of the LTTng-UST end user interface
(are these stable between release) ?
If so, I will gladly give it a try !
From: Thibault, Daniel [daniel.thiba...@drdc-rddc.gc.ca]
Sent: Monday, October
-Message d'origine-
De : Boisvert, Sebastien [mailto:boisv...@anl.gov]
Envoyé : 20 octobre 2014 11:38
Are TRACEPOINT_EVENT_CLASS and
TRACEPOINT_EVENT_INSTANCE part of the LTTng-UST end user interface (are these
stable between release) ?
If so, I will gladly give it a try !
As
From: Eugene Ivanov [e...@tbricks.com]
Sent: Monday, October 20, 2014 6:01 AM
To: Boisvert, Sebastien
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] Best way to analyze CTF files
Hi Sebastian,
*Sebastien* or *Sébastien*
In our company one of the main lttng applications is
Thanks for testing.
I will use these.
Can I add Suggested-by: Daniel Thibault daniel.thiba...@drdc-rddc.gc.ca in
our open source
BIOSAL git log ?
From: Thibault, Daniel [daniel.thiba...@drdc-rddc.gc.ca]
Sent: Monday, October 20, 2014 10:43 AM
To:
-Message d'origine-
Envoyé : 20 octobre 2014 11:51
Thanks for testing.
I will use these.
Can I add Suggested-by: Daniel Thibault daniel.thiba...@drdc-rddc.gc.ca
in our open source BIOSAL git log ?
Absolutely!
I also take cash, money orders, cheques and payment in kind.
___
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.lttng.org/pipermail/lttng-dev/attachments/20141020/d05b31bc/attachment.html
Hey,
That's pretty cool! Do you have any thoughts on the LifoSem implementation in
folly? What are the differences in design decisions between your workqueue and
lifosem?
One other folly abstraction you might want to look at is MPMCQueue -- this is
our fifo workqueue that we combine with
Greetings everyone (including LTTng bards!),
The lttng-tools project provides a session daemon (lttng-sessiond) that acts as
a tracing registry, the lttng command line for tracing control, a lttng-ctl
library for tracing control and a lttng-relayd for network streaming and live
reading.
This is
Note that there are now new lines for parsing efficiency. You can find the XML
I think you meant there are _no_ new lines! With the typo, it means
the exact opposite. :)
A small tip for those who are going to work with the MI, use xmllint
to format the output nicely when you want to read it
Hi Genevive,
I have found the sollution. Actually, I have replaced the CtfEvent and
CtfIterator by ITmfEvent and ITmfContext. This allows me to read the both
the latest and old format. The sample code is attached below, in case if
some one comes across the same problem.
Best regards,
Shariyar
Hi All,
if relayd gets killed i see there is connection reset which happens at
client.
Is there a way to relaunch the sessiond/consumerd on a connection reset?
can some hooks be added or helper application be written to relaunch
sessiond in case exit of relayd or any other connection reset?
one more point:
if there is a way to kill/exit sessiond on a connection reset then will be
easier to re-launch it again
wondering if anything of that sort can be done
Thanks,
Anand Neeli
On Tue, Oct 21, 2014 at 12:02 AM, Anand Neeli anand.ne...@gmail.com wrote:
Hi All,
if relayd gets killed
Hello
I just tried to configure the metadata channel for UST. After that I get
an error when listing the session.
Could someone please verify this? See below for the commands I used and
the error message.
Many thanks in advance!
Best Regards
Bernd
lttng create
Session auto-20141020-141307
Merged, thanks a lot !!
Mathieu
- Original Message -
From: Nathan Lynch nathan_ly...@mentor.com
To: lttng-dev@lists.lttng.org
Sent: Saturday, October 18, 2014 3:00:23 PM
Subject: [lttng-dev] [PATCH] lttng-modules: fix build for non-x86
Since commit
Hi Daniel,
TRACEPOINT_EVENT_CLASS + TRACEPOINT_EVENT_INSTANCE work.
Thanks.
The documentation is in include/lttng/ust-tracepoint-event.h (lttng-ust) and
the last change was made
in 2011:
1c324e59 (Mathieu Desnoyers 2011-11-18 12:36:52 -0500 63) /*
1c324e59 (Mathieu Desnoyers 2011-11-18
Greetings everyone (including LTTng bards!),
The lttng-tools project provides a session daemon (lttng-sessiond) that
acts as a tracing registry, the lttng command line for tracing
control, a lttng-ctl library for tracing control and a lttng-relayd for
network streaming and live reading.
This is
LTTng-UST, the Linux Trace Toolkit Next Generation Userspace Tracer, is
port of the low-overhead tracing capabilities of the LTTng kernel tracer
to user-space. The library liblttng-ust enables tracing of
applications and libraries.
This is a small bugfix release.
Changelog:
2014-10-20 lttng-ust
The LTTng modules provide Linux kernel tracing capability to the LTTng
2.x tracer toolset.
This is a bugfix release.
Changelog:
2014-10-20 LTTng modules 2.5.1
* Print build warning when writeback probe is disabled
* Fix compilation on Ubuntu 14.10
* Fix: compile
Signed-off-by: Mathieu Desnoyers mathieu.desnoy...@efficios.com
---
src/common/kernel-ctl/kernel-ioctl.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/common/kernel-ctl/kernel-ioctl.h
b/src/common/kernel-ctl/kernel-ioctl.h
index c88f970..475a066 100644
---
The LTTng modules provide Linux kernel tracing capability to the LTTng
2.x tracer toolset.
New noteworthy features in this release:
- System call filtering! Fine-tune which system calls you want
to trace or not,
- We now gather in/out parameters of system calls at entry and
exit of the
23 matches
Mail list logo
