Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] [RELEASE] Babeltrace 1.1.2
Date: Fri, 28 Feb 2014 18:11:32 +0000 (UTC)	[thread overview]
Message-ID: <1534324216.32381.1393611092080.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <357348868.32380.1393611075527.JavaMail.zimbra@efficios.com>

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.


Changelog:
2014-02-28 Babeltrace 1.1.2
        * Cleanup: remove logically dead code
        * Fix: ctf.c fscanf missing integer length check
        * Add J?r?mie Galarneau as co-maintainer
        * Fix: disallow re-using same event ID in same stream
        * Fix: check for unknown enum/variant fields
        * Fix: libbabeltrace lib build dependencies
        * Be more widely accepting for missing variant/enum fields
        * Refuse 0 integer size
        * Fix: read/write mode check
        * Cleanup: do not duplicate code in float fix
        * Fix: floats should set content size in tmp definition
        * Fix: test content size vs headers len
        * Fix: test for less than 1 byte packets
        * Fix: reversed logic in packet vs content size
        * Fix: clarify end of packet error
        * Fix: string packet boundary handling, bits vs bytes
        * Fix: add stricter checks on packet boundaries
        * Cleanup: fix typo
        * Fix: fail when reading 0 byte event
        * Fix: Take the iterator's end position into account
        * Fix: Use the bt_iter_set_pos function to set the begin_pos
        * Fix: Don't create a new packet if ctf_move_pos() seeks out of a packet
        * Fix: Uninitialized ctf_stream_pos structure in ctf_float_write()
        * Fix: Use the packet's final size when mmap-ing the next packet
        * Fix: Close traces on context destruction
        * gcc warning fix: -Wextra
        * Declare enum type to use from C++
        * Tests: fix string octal encoding
        * Fix ctf_clock_declaration_visit returning an error when reading a boolean
        * Fix CTF parser hang with bison 3.0
        * Add missing lex/bison generated files to make clean
        * Test for presence of bison and flex when building from git
        * Fix: Unchecked asprintf/vasprintf return values
        * Missing NULL pointer init in tap.c
        * Document: manpage: chronologically ordered events
        * Cleanup: comment mismatch with code
        * Cleanup: remove whitespaces at end of lines

Project website: http://www.efficios.com/babeltrace
Download link: http://www.efficios.com/files/babeltrace/
CTF specification: http://www.efficios.com/ctf

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com



           reply	other threads:[~2014-02-28 18:11 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <357348868.32380.1393611075527.JavaMail.zimbra@efficios.com>]

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=1534324216.32381.1393611092080.JavaMail.zimbra@efficios.com \
    --to=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