From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org,
diamon-discuss@lists.linuxfoundation.org,
linux-trace-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RELEASE] LTTng-UST 2.13.9 (Linux user-space tracer)
Date: Mon, 14 Apr 2025 16:51:40 -0400 [thread overview]
Message-ID: <e30fec58-25c0-4de7-8d03-23c1f6a903a1@efficios.com> (raw)
Hi,
This is a release announcement of LTTng-UST 2.13.9.
Noteworthy in this bug fix release:
* Use UATOMIC_HAS_ATOMIC_{BYTE,SHORT} to fix build against
liburcu 0.15.2.
* Add a close_range declaration in the liblttng-ust-fd.so wrapper.
And other minor fixes, see the detailed change log below.
LTTng-UST, the Linux Trace Toolkit Next Generation Userspace Tracer,
is a low-overhead application tracer. The library "liblttng-ust" enables
tracing of applications and libraries.
* Detailed change log:
2025-04-14 (National Gardening Day) lttng-ust 2.13.9
* Fix: Use UATOMIC_HAS_ATOMIC_{BYTE,SHORT} for counter atomics
* Fix: lttng-ust-tp regex warnings
* lttng-ust-java: Load lttng-ust-context-jni before other JNI libraries
* doc/examples: set minimal CMake version to 3.5.0
* Fix: Update `get_mempolicy` check to handle `EPERM`
* Fix: Correct `numa_available` return code checks
* Fix: test_benchmark: do not match "CPU(s) scaling MHz:"
* Tests: Fix abi conflict test when building with clang
* Fix: Build examples when rpath is stripped from in-build-tree libs
* ust-fd: Add close_range declaration
* docs: Correct GitHub URLs in lttng-ust.3
* fix: handle EINTR correctly in get_cpu_mask_from_sysfs
Project website: https://lttng.org
Documentation: https://lttng.org/docs
Download link: https://lttng.org/download
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
reply other threads:[~2025-04-14 20:51 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=e30fec58-25c0-4de7-8d03-23c1f6a903a1@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=mathieu.desnoyers@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