From: jeremie.galarneau@efficios.com (Jérémie Galarneau)
Subject: [lttng-dev] [RELEASE] LTTng-Tools 2.9.12 - Joannès
Date: Fri, 24 May 2019 17:33:53 -0400 [thread overview]
Message-ID: <20190524213352.GC9974@gmail.com> (raw)
Hi all,
The twelfth bug-fix release of LTTng-Tools 2.9 - Joann?s has just been
released. This release addresses a number of issues listed below.
2019-05-24 lttng-tools 2.9.12 (Asparagus Day)
* Update base test for binding
* Fix: python binding: expose domain buffer type
* Fix: logging: log_add_time() save/restore errno
* Fix relayd: initialize beacon to -1ULL
* Fix: relayd: handling of lttng_read errors >= 0
* Fix tests: NULL pointer dereference in ust channel unit tests
* Fix tests: NULL pointer dereference in ltt_ust_context unit tests
* Log the wait-shm's path on shm_open failure
* Fix: skip test when ust doesn't have perf support
* Fix: Properly sanitize input parameter
* tap-driver.sh: flush stdout after each test result
* Fix tests: snapshot size validation failure runs too many test cases
* Fix tests: the tree origin can be a symlink itself
* Fix tests: skip test_getcpu_override on single core systems
* Fix: consumer snapshot: handle unsigned long overflow
* Fix: wrong error code returned by kernel_snapshot_record()
* Docs: document the format of the lttng_session path member
* Fix: check illegal combinations of ctrl-url/data-url/ouput/set-url
* Tests: take multiple snapshots in streaming mode
* Fix: don't destroy the sockets if the snapshot was successful
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.9.12.tar.bz2
GPG sig:
https://lttng.org/files/lttng-tools/lttng-tools-2.9.12.tar.bz2.asc
reply other threads:[~2019-05-24 21:33 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=20190524213352.GC9974@gmail.com \
--to=jeremie.galarneau@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