From: dgoulet@efficios.com (David Goulet)
Subject: [lttng-dev] [RELEASE] LTTng-Tools 2.2.6
Date: Fri, 28 Feb 2014 12:59:26 -0500 [thread overview]
Message-ID: <20140228175926.GB14281@thessa> (raw)
Greetings everyone (including LTTng elves),
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.
This is the last stable 2.2 release and thus it will not be supported anymore
after this.
2014-02-28 lttng-tools 2.2.6
* Fix: remove break in epoll loop of apps. thread
* Fix: remove bad code from previous backport patch
* Fix: bad logical check of error codes
* Fix: resource leak in enable-event command
* Fix: unchecked return value in ust app delete
* Fix: dereference after null check in UST registry
* Fix: Resource leak in ust registry
* Fix: backported from urcu commit 92af1a30
* Fix: add missing values for a backported fix
* Fix: update back the metadata len sent on failure
* Fix: don't fail on push metadata if no channel
* Fix: comparison of unsigned enum expression >= 0
* Fix: implicit conversion of enum types in sessiond
* Fix: comparison of unsigned value agains < 0
* Add libuuid as dependency in README
Please report ANY issues to bugs.lttng.org or through that mailing list.
Using it is testing it!
Project website: http://lttng.org/lttng2.0
Download link:
http://lttng.org/files/lttng-tools/lttng-tools-2.2.6.tar.bz2 (for
the PGP signature, same file with .asc appended)
Cheers!
David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 603 bytes
Desc: Digital signature
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20140228/1a655296/attachment.pgp>
reply other threads:[~2014-02-28 17:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140228175926.GB14281@thessa \
--to=dgoulet@efficios.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