From: jeremie.galarneau@efficios.com (Jérémie Galarneau)
Subject: [lttng-dev] [RELEASE] Babeltrace 1.5.0-rc1
Date: Mon, 24 Oct 2016 14:56:11 -0400 [thread overview]
Message-ID: <CA+jJMxsDzCxCm5otykD6MRezCC-skNondt=XUb0_=0wyZDJzJg@mail.gmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2051 bytes --]
Hi all,
Today we are releasing the first release candidate of Babeltrace 1.5.
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 release adds two features to the CTF Writer library:
* Allow the definition of custom stream packet headers
* Validation utility to check for reserved CTF identifiers
Change log:
2016-10-24 babeltrace 1.5.0-rc1 (First barrel ride down Niagara Falls)
* Update version to 1.5.0
* Python build fix
* Fix enum rename warnings
* Hide bt_ctf_writer_get_trace()
* Hide bt_ctf_trace_* symbols
* Hide get_field_paths_lca_index()
* Remove bt_ctf_writer_add_environment_field_int64
* Hide new bt_ctf_stream_* symbols
* Hide new bt_ctf_stream_class_* symbols
* Hide new bt_ctf_field_type_* symbols
* Hide new bt_ctf_packet_* symbols
* Hide new bt_ctf_field_* symbols
* Hide new bt_ctf_field_path_* symbols
* Hide new bt_ctf_event_* symbols
* Hide bt_ctf_event_class_* symbols
* Hide new bt_ctf_clock_* symbols
* Hide bt_get and bt_put
* Hide bt_values and bt_attributes in libbabeltrace-ctf
* Backport the CTF-IR interface
* debug info: Call register_event_debug_infos for all events
* Typo: configure.ac implemenation -> implementation
* configure: fix uuid support detection on static build
* Tests: no substitution needed for multi-trace intersection test
Project website: http://diamon.org/babeltrace/
Download link: http://www.efficios.com/files/babeltrace/babeltrace-1.5.0-rc1.tar.bz2
CTF specification: http://diamon.org/ctf/
Jérémie
--
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com
reply other threads:[~2016-10-24 18:56 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='CA+jJMxsDzCxCm5otykD6MRezCC-skNondt=XUb0_=0wyZDJzJg@mail.gmail.com' \
--to=jeremie.galarneau@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