archive mirror
 help / color / mirror / Atom feed
From: "Jérémie Galarneau" <>
Subject: [RELEASE] Babeltrace 2.0.2 - Amqui
Date: Tue, 10 Mar 2020 19:06:13 -0400	[thread overview]
Message-ID: <> (raw)

Hi everyone!

Today we're releasing the first patch-level release of Babeltrace 2.0

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: silently accepting invalid Python configuration
	* Cleanup: 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:

Babeltrace website:

Mailing list (for support and development):
    `lttng-dev at`

IRC channel:
    `#lttng` on ``

Git repository:

GitHub project:

Continuous integration:

Code review:


                 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:

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

  git send-email \ \ \ \ \
    --subject='Re: [RELEASE] Babeltrace 2.0.2 - Amqui' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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