From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] [RELEASE] Babeltrace 1.0.2
Date: Fri, 11 Jan 2013 09:51:10 -0500 [thread overview]
Message-ID: <20130111145110.GA15036@Krystal> (raw)
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.
Please note that the 1.0.1 tarball does not build, this is why we skip
from 1.0.0 to 1.0.2 directly.
Changelog:
2012-01-11 Babeltrace 1.0.2
* Fix: add tests/lib missing files to Makefile.am
2012-01-11 Babeltrace 1.0.1
* Provides a basic pkg-config file for libbabeltrace
* Fix erroneous warning/error messages
* Fix comment in context.h
* Cleanup: Remove whitespace at EOL from mit-license.txt
* Add missing permission notice in each source file
* Adding a test which do a sequence of seek BEGIN, LAST, BEGIN, LAST
* Run seek tests on a second trace file
* Add #define _GNU_SOURCE to remove warning about asprintf
* Include a test for SEEK_BEGIN and SEEK_LAST
* Fix: Report success even if we find at least one valid stream in find_max_timestamp_ctf_stream_class
* Fix SEEK_BEGIN for streams that do not contain any event
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:[~2013-01-11 14:51 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=20130111145110.GA15036@Krystal \
--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