From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: lttng-dev <lttng-dev@lists.lttng.org>
Cc: diamon-discuss@lists.linuxfoundation.org,
linux-trace-users@vger.kernel.org
Subject: [RELEASE] LTTng-UST 2.13.1 (Linux user-space tracer)
Date: Fri, 10 Dec 2021 15:45:38 -0500 (EST) [thread overview]
Message-ID: <1697490258.28441.1639169138969.JavaMail.zimbra@efficios.com> (raw)
This 2.13.1 release of LTTng-UST is a bugfix-only release for various
shortcomings that were identified in the 2.13.0 release.
A few key highlights: the C++ support for building probe providers has
been improved, async-signal-safety of the close wrapper has been fixed,
pthread cancelstate in nested use scenarios is now properly handled.
2021-12-10 (Lost and Found Day) lttng-ust 2.13.1
* Fix: ust-compiler: constructor/destructor build on g++ 4.8
* ust-compiler: constructor/destructor whitespaces layout and macro dependency
* Fix: ust-cancelstate: include string.h for strerror
* Fix: libnuma is prepended to LIBS
* fix: Allow disabling some abi compat tests
* Fix: generate probe registration constructor as a C++ constuctor
* Fix: nestable pthread cancelstate
* Fix: abort on decrement_sem_count during concurrent tracing start and teardown
* fix: allocating C++ compound literal on heap with Clang
* Check for C++11 when building C++ probe providers
* fix: liblttng-ust-fd async-signal-safe close()
* tracepoints: print debug message when lttng-ust-tracepoint.so is not found
* Fix: static_assert unavailable with glibc < 2.16
* Fix: combined tracing of lttng-ust 2.12/2.13 generates corrupted traces
* doc/man: Document LTTNG_UST_ABORT_ON_CRITICAL variable
* fix: remove autoconf features default value in help message
* Set git-review branch to stable-2.13
* Fix: add extern "C" to two header files
Project website: https://lttng.org
Documentation: https://lttng.org/docs
Download link: https://lttng.org/download
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
reply other threads:[~2021-12-10 20:45 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=1697490258.28441.1639169138969.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@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).