archive mirror
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <>
To: lttng-dev <>
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: <> (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 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:
Download link:

Mathieu Desnoyers
EfficiOS Inc.

                 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).