From: "Jérémie Galarneau" <jeremie.galarneau@efficios.com>
To: lttng-dev@lists.lttng.org
Cc: diamon-discuss@lists.linuxfoundation.org,
linux-trace-users@vger.kernel.org
Subject: [RELEASE] LTTng-tools 2.13.4 - Nordicité
Date: Thu, 27 Jan 2022 15:35:39 -0500 [thread overview]
Message-ID: <YfMCG9NUWn+iIXV8@Mercury> (raw)
Hi all,
We have just released the third bug-fix release of LTTng-tools 2.13 - Nordicité.
This release addresses a number of issues listed below.
2022-01-26 lttng-tools 2.13.4 (National Peanut Brittle Day)
* Build fix: hashtable: hashtable.cpp does not exist
* Fix: _lttng_variant_statedump should expect lttng_ust_ctl_atype_variant_nestable
* Fix context mismatch across UST version due to legacy array context field
* Relicence all source and header files included in LGPL code
* Move utils_expand_path and utils_expand_path_keep_symlink to libpath.la
* Link lttng executable on libcommon-lgpl.a
* Introduce libcommon-lgpl for liblttng-ctl
* Rename libcommon.so to libcommon-gpl.so
* Copyright ownership transfer
* Copyright ownership transfer
* Fix: relayd: erroneous rundir permission logging message
* Fix: sessiond: rotation thread: fatal error when not finding a session
* Fix: relayd: rotation failure for multi-domain session
* Fix: lttng-ctl: lttng_list_sessions: initialize out_sessions to NULL when returning 0
* Fix: lttng: initialize variable in run_command_string
* Fix: consumer-stream: live viewers observe timestamps going backwards
* Fix: relayd: ressource leaks on viewer_stream_create error
* Fix: relayd: live: erroneous message timestamp observed from live viewer
* Fix: relayd: failure to open chunk files concurrently with session clear
* Fix: relayd: live: metadata stream reference count < 0 assert
Note that v2.13.3 was tagged nearly simultaneously as this release, but
unannounced since a bad backport caused the generation of the tarball to fail.
The change log above combines the changes relevant to both releases.
As always, please report any issue you may encounter to bugs.lttng.org
or on this mailing list.
Project website: https://lttng.org
Download link:
https://lttng.org/files/lttng-tools/lttng-tools-2.13.4.tar.bz2
GPG signature:
https://lttng.org/files/lttng-tools/lttng-tools-2.13.4.tar.bz2.asc
reply other threads:[~2022-01-27 20:35 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=YfMCG9NUWn+iIXV8@Mercury \
--to=jeremie.galarneau@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=lttng-dev@lists.lttng.org \
/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;
as well as URLs for NNTP newsgroup(s).