----- On Jun 14, 2017, at 4:43 AM, Thomas McGuire [email protected] wrote:
> Hi, > > I have a recurring problem of tools like babeltrace and TraceCompass > exiting because of an allocation failure. > > For example running babeltrace on a captured trace leads to babeltrace > processing some events, and then exiting with: > GLib-ERROR **: gmem.c:168: failed to allocate 17179869184 bytes > > This sounds like a corrupted trace file to me. Or maybe a version or > format mismatch? > > In case it helps, babeltrace's backtrace at that point is attached to > the mail. > > I'm using lttng-relayd 2.9.4 on the host, and lttng 2.9.4 on an i.MX25 > device. Babeltrace is at version 1.5.1. > The same problem can be seen when not using lttng-relayd. > > I've also seen other problems like "[error] Event id 3336003216 is > outside range." > > lttng-sessiond shows no warnings or errors during recording, and neither > does lttng start or stop - not even lost events. > > Any idea how the trace file got corrupted and how I can record traces > without corruption in the future? Can you provide a copy of the metadata file ? And ideally the data streams too ? This would give us a better idea of what is happening. Do you perform kernel or user-space tracing ? Do you trace huge sequences of bytes within your own tracepoints ? Thanks, Mathieu > > Thanks, > Thomas > -- > Thomas McGuire | [email protected] | Senior Software Engineer > KDAB (Deutschland) GmbH&Co KG, a KDAB Group company > Tel: +49-30-521325470 > KDAB - The Qt Experts > > _______________________________________________ > lttng-dev mailing list > [email protected] > https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com _______________________________________________ lttng-dev mailing list [email protected] https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
