Skip to contentSkip to conversation

Babel trace is throwing error while trying with -i lttng-live option

DISCUSSION Jérémie Galarneau 1 participant 1 message Feb 13, 2015 1 message not in the archive

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive
Quoted 8 lines · Ranganadh Kanitmahanti

Hi,

************************************************
[error] Unexpected end of packet. Either the trace data stream is corrupted or metadata description does not match data layout. [error] Reading event failed.
Error printing trace.

Quoted 8 lines

************************************************

Can any body tell about this significance. I have seen a similar bug resolved Bug #686: stream parser should have a clearer error message when encountering cross-packet fields - Babeltrace - LTTng bugs repository
<https://bugs.lttng.org/issues/686>
Can anybody tell in which version the fix was released.

The fix only clarifies the error message. The corrupted stream probably can't be handled by Babeltrace anymore at that point. To answer your question, that fix was introduced in v1.1.2 and is part of all v1.2.x releases.

Can you give us more information to reproduce the problem? Which version of LTTng-Tools and Babeltrace are you using?

Thanks,
Jérémie

Quoted 20 lines

Bug #686: stream parser should have a clearer error message when encountering cross-packet fields -... <https://bugs.lttng.org/issues/686>
Redmine
View on bugs.lttng.org <https://bugs.lttng.org/issues/686>
Preview by Yahoo

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Signature · 3 lines
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev