[lttng-dev] [RELEASE] Babeltrace 1.0.0-rc1

[lttng-dev] [RELEASE] Babeltrace 1.0.0-rc1

[Mathieu Desnoyers]

From this point on (Release Candidate 1), Babeltrace 1.0 enters feature
freeze mode. From this point on, only bugfixes will enter into
the following release candidates. We should expect to see 1.0 final in a
few weeks from now.

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:

2012-04-18 Babeltrace 1.0.0-rc1
        * Fix: -n "field names" option should allow "none"
        * Fix: Show context field name by default
        * Manpage fix: babeltrace-log manpage should refer to lttng(1)
        * Clarify warning message for events discarded
        * Fix: babeltrace should skip erroneous traces
        * Fix: put explicit error messages and warnings when opening a trace
        * Fix: segfault on error handling
        * Fix: enum must use last value + 1 as next item value
        * Fix: warn, and don't assert, when reading a value outside enum range
        * API Fix : missing list fields of event decl
        * API fix : fill the values for timestamp begin and end
        * API : list of events in the trace
        * UUID field should be optional, as specified by CTF spec
        * Babeltrace ctf-text duplicated error message
        * API fix/breakage : reexporting bt_ctf_event
        * fix/breakage API : replace bt_ctf_event
        * add ctf_event_definition pointer to ctf_stream_definition
        * Rename ctf_event to ctf_event_declaration
        * Rename ctf_stream to ctf_stream_definition
        * Rename ctf_stream_event to ctf_event_definition
        * Rename ctf_stream_class to ctf_stream_declaration
        * Cleanup: Remove unneeded local variables from function
        * API Fix : give access to trace_handle and context
        * API Fix : handle id to use the public functions
        * Fix : add the missing seek begin

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

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com

[lttng-dev] babeltrace-log

[Oestman, Fredrik]

Mathieu Desnoyers wrote:
> The "babeltrace-log" command converts from a text log to a CTF trace.

I did this:

$ babeltrace --no-delta --clock-seconds --clock-raw combined > combined.log
$ babeltrace-log combined_new < combined.log
$ babeltrace --no-delta --clock-seconds --clock-raw combined_new > combined_new.log
[error] Invalid magic number 0x2BCAB7F7 at packet 196 (file offset 6422528).
[error] Open file stream error.
[warning] [Context] Cannot open_trace of the format combined.ctf .

[warning] [Context] opening trace "combined.ctf" from combined.ctf for reading.

Am I doing something obviously wrong, or is just a bit more care needed when using babeltrace-log?

"combined" is a trace containing events in both kernel and ust domains.


Cheers,

Fredrik ?stman

[lttng-dev] babeltrace-log

[Mathieu Desnoyers]

* Oestman, Fredrik (Fredrik_Oestman at mentor.com) wrote:
> Mathieu Desnoyers wrote:
> > The "babeltrace-log" command converts from a text log to a CTF trace.
> 
> I did this:
> 
> $ babeltrace --no-delta --clock-seconds --clock-raw combined > combined.log
> $ babeltrace-log combined_new < combined.log
> $ babeltrace --no-delta --clock-seconds --clock-raw combined_new > combined_new.log
> [error] Invalid magic number 0x2BCAB7F7 at packet 196 (file offset 6422528).
> [error] Open file stream error.
> [warning] [Context] Cannot open_trace of the format combined.ctf .
> 
> [warning] [Context] opening trace "combined.ctf" from combined.ctf for reading.
> 
> Am I doing something obviously wrong, or is just a bit more care needed when using babeltrace-log?

make sure you have an up to date babeltrace version. If the problem
persists with an updated version, can you send me a link to your
original "combined" trace files ? (a .tar.gz would be perfect).

This use-case works fine here.

Please note that babeltrace-log will simply take a text log and save
each line into a CTF trace (as a string).

Thanks,

Mathieu

> 
> "combined" is a trace containing events in both kernel and ust domains.
> 
> 
> Cheers,
> 
> Fredrik ?stman
> 
> 
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com