[lttng-dev] [RELEASE] Babeltrace 1.4.0

[Jérémie Galarneau]

Hi all,

Babeltrace 1.4 has just been released!

The Babeltrace project provides trace read and write libraries, as well
as a trace converter. Plugins can be created for any trace format to
allow its conversion to/from another trace format.

The main format expected to be converted to/from is the Common Trace
Format (CTF). The default input format of the "babeltrace" command is
CTF, and its default output format is a human-readable text log. The
"babeltrace-log" command converts from a text log to a CTF trace.


This new version introduces a number of new features:

* Debug Information printing
The babeltrace debug info analysis is a set of features which allow
mapping events from a trace to their location in source code or within
a binary file, based on their `ip` (instruction pointer) field.

This new feature works in conjunction with LTTng UST 2.8's new
shared object base address state dump events and introduces
an optional dependency on elfutils >= 0.154.

More information on this feature is available here:
https://raw.githubusercontent.com/efficios/babeltrace/stable-1.4/doc/debuginfo.txt

* Stream Intersection
This feature adds a new command line option "--stream-intersection" to the
babeltrace executable forcing it to only display events that fit in the
intersection of a trace's streams, thus filtering out time spans for which only
some streams' events are available. This is achieved by using the packet
header timestamp begin/end information available within each stream.

Opening multiple traces using either the babeltrace binary or the Python
TraceCollection interface will result in the reading of the union of every
traces' stream intersection.

The Python TraceCollection interface now accepts an "intersect_mode"
parameter to expose this feature to scripts.

* Lost packet reporting
Starting from LTTng 2.8, a packet sequence number is stored as part
of traces' packet context. This allows babeltrace (and other viewers) to
report lost packets when the "overwrite" mode is being used.

This version of Babeltrace takes advantage of this new context field to
report lost packets in the same way discarded events were previously
reported.

See the LTTng documentation for more information on discard and
overwrite modes:
https://lttng.org/docs/#doc-channel-overwrite-mode-vs-discard-mode

2016-06-06 babeltrace 1.4.0 (National Yo-Yo Day)
        * Tests: dereference of NULL pointer on allocation failure
        * Tests: abort dwarf test on open() failure
        * Fix: lttng-live does not set a trace descriptor
        * Tests: Add missing --merge LOG_DRIVER_FLAGS
        * Fix: strerror_r behavior is glibc specific
        * sys/param.h is required for MAXNAMLEN on musl libc
        * Fix: undefined bit shift operation when printing octal numbers
        * Fix: Wrong variable checked in bin_info_child_die_has_address
        * Fix: Only close valid fds in is_valid_debug_file
        * Fix: Free die_name in bin_info_lookup_cu_function_name
        * Fix: Don't dereference null ptr in error path
        * Standardise spelling of debug info
        * Fix: typo in --disable-debug-info in configure error message
        * Docs: change --clock-raw to --clock-cycles
        * Fix: segmentation fault with multi-trace having non-correlated clocks

Project website: http://diamon.org/babeltrace/
Download link: http://www.efficios.com/files/babeltrace/babeltrace-1.4.0.tar.bz2
CTF specification: http://diamon.org/ctf/

-- 
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com