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

[Jérémie Galarneau]

On Mon, Feb 16, 2015 at 5:33 AM, Ranganadh Kanitmahanti <
ranganadh1991 at yahoo.com> wrote:

> hi,
> We are using babeltrace 1.2.4 and LTTng Trace Control 2.5.3.  Continously
> giving babeltrace is throwing this error. Sorry about previous
> conversation. I am actually getting this reading a snapshot session . I
> have given continously babeltrace and path to read the traces . Then I am
> getting this error.
> We see below mentioned error while reading out traces using babeltrace…
>

Okay, so "live" is not involved at all here?
Would it be possible to share the trace?

Also, can you provide the commands issued to capture this trace?

Thanks,
Jérémie


>
>
> ************************************************
> [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.
>
> ************************************************
>
> Thanks & Regards,
> K.V.Ranganadh.
>
>
>   On Monday, 16 February 2015 2:26 PM, Ranganadh Kanitmahanti <
> ranganadh1991 at yahoo.com> wrote:
>
>
> Hi,
>
> We are using "BabelTrace Trace Viewer and Converter 1.2.4 "
>
> Thanks & Regards,
> K.V.Ranganadh.
>
>
>   On Friday, 13 February 2015 8:19 PM, Jérémie Galarneau <
> jeremie.galarneau at efficios.com> wrote:
>
>
>
>
> On Fri, Feb 13, 2015 at 12:47 AM, Ranganadh Kanitmahanti <
> ranganadh1991 at yahoo.com> wrote:
>
> 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.
>
> ************************************************
>
> 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
>
>
>
>
>
>
>
>
> 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
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
>
>
>
> --
> Jérémie Galarneau
> EfficiOS Inc.
> http://www.efficios.com
>
>
>
>
>


-- 
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20150216/14e32db8/attachment.html>