Thanks for the update Jérémie. When something is not working and you are looking for an explanation, blobs of binary in a mostly text file ring alarm bells. I’m impressed that the parser for the metadata can deal with this. It is very helpful to have a reference like this on the mailing list for future devs looking for answers.
Thanks to you all. From: [email protected] [mailto:[email protected]] On Behalf Of Jeremie Galarneau Sent: Thursday, March 05, 2015 4:50 PM To: Neil Bryan Cc: [email protected]; [email protected] Subject: Re: [lttng-dev] LTTng 2.6.0: Corrupt metadata? On Thu, Mar 5, 2015 at 8:58 AM, Neil Bryan <[email protected]<mailto:[email protected]>> wrote: From my first post: If I try and parse recovered traces using Babeltrace, it fails with a segmentation fault. nbryan@meteorubuntu-OptiPlex-7010:/data/nbryan/Meteor/altera_trace$ babeltrace --help BabelTrace Trace Viewer and Converter 1.0.0-rc1 nbryan@meteorubuntu-OptiPlex-7010:/data/nbryan/Meteor/altera_trace$ babeltrace auto-20150304-091109/ Segmentation fault (core dumped) I downloaded, built and installed this version: nbryan@meteorubuntu-OptiPlex-7010:/data/nbryan/Meteor/altera_trace$ babeltrace --help BabelTrace Trace Viewer and Converter 1.2.4 And it now parses the captured traces. This is interesting as maybe the metadata is well-formed after all! I shall now investigate the Eclipse-side of things. Glad to know it all worked out! To add to Glen's great explanation, the binary blobs you see mid-way in the metadata file are padding + the next packet's header. The amount of padding is the difference between the packet_size and the content_size. Jérémie _______________________________________________ lttng-dev mailing list [email protected]<mailto:[email protected]> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev -- 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
