From: "Jérémie Galarneau" <jeremie.galarneau@efficios.com>
To: lttng-dev@lists.lttng.org, diamon-discuss@lists.linuxfoundation.org
Subject: [diamon-discuss] [RELEASE] Babeltrace 2.0.2 - Amqui
Date: Tue, 10 Mar 2020 19:06:13 -0400 [thread overview]
Message-ID: <20200310230613.GA234639@gmail.com> (raw)
Hi everyone!
Today we're releasing the first patch-level release of Babeltrace 2.0
"Amqui".
What's new since Babeltrace 2.0.1?
==================================
This release contains the following note-worthy fixes:
- Fixed a segmentation fault when trying to instantiate a trimmer
downstream of a component that creates streams without packets.
See 5cf4fb3d2 [1].
- The trimmer component class rejected streams that are not
packetized. Since the trimmer supports streams without packets,
there is no reason to reject them.
See a26dd09ff [2].
- The configure script silently accepted invalid Python
configurations such as building with `--enable-python-plugins`,
but without `--enable-python-bindings`, which resulted in users
being unable to import the `bt2` package.
See 3530dd01a [3].
The full change log follows.
2020-03-10 Babeltrace 2.0.2 (International Bagpipe Day)
* common: cast arguments to character classification functions to unsigned char
* flt.utils.muxer: initialize variable to silence -Wmaybe-uninitialized warning
* Fix: configure.ac: silently accepting invalid Python configuration
* Cleanup: configure.ac: remove redundant `AC_ARG_ENABLE` parameters
* Fix: plugin-dev.h: Disable address sanitizer on pointer array section variables
* Fix: cli: use BT_CLI_LOGE_APPEND_CAUSE instead of printf to print errors
* tests: improve flt.utils.trimmer/test_trimming to test streams without packets
* Fix: flt-utils.trimmer: accept streams without packet support
* Fix: lib: don't assume that streams have packets in auto seek
* Fix: correct typo in README
* Update working version to Babeltrace 2.0.2
Important links
===============
Babeltrace 2.0.2 tarball:
https://www.efficios.com/files/babeltrace/babeltrace2-2.0.2.tar.bz2
Babeltrace website:
https://babeltrace.org
Mailing list (for support and development):
`lttng-dev at lists.lttng.org`
IRC channel:
`#lttng` on `irc.oftc.net`
Git repository:
https://bugs.lttng.org/projects/babeltrace
GitHub project:
https://github.com/efficios/babeltrace
Continuous integration:
https://ci.lttng.org/view/Babeltrace/
Code review:
https://review.lttng.org/q/project:babeltrace
[1] https://github.com/efficios/babeltrace/commit/5cf4fb3d2
[2] https://github.com/efficios/babeltrace/commit/a26dd09ff
[3] https://github.com/efficios/babeltrace/commit/3530dd01a
reply other threads:[~2020-03-10 23:06 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=20200310230613.GA234639@gmail.com \
--to=jeremie.galarneau@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.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