[lttng-dev] not able to read 32-bit app traces running on a 64-bit system with relayd

[Jérémie Galarneau]

On Tue, Dec 2, 2014 at 8:01 AM, Anand Neeli <anand.neeli at gmail.com> wrote:
> Hi All,
> I have verified that i'm able to read the attached 32-bit and 64-bit traces
> using eclipse trace compass.
> Where as babeltrace fails to read 32-bit traces.
> Can anyone please let me know what could be the issue here.
>

Deleting the index folder of the 32 bit trace seems to make it
possible for babeltrace to read the trace... Reproducible on
Babeltrace master.

Would you mind opening a bug report against Babeltrace on bugs.lttng.org?

Thanks,
Jérémie

> Thanks,
> Anand Neeli
>
> ---------- Forwarded message ----------
> From: Anand Neeli <anand.neeli at gmail.com>
> Date: Thu, Nov 27, 2014 at 5:01 PM
> Subject: not able to read 32-bit app traces running on a 64-bit system with
> relayd
> To: "lttng-dev at lists.lttng.org" <lttng-dev at lists.lttng.org>
>
>
> Hi All,
> I'm running both 32-bit and 64-bit app's on a 64-bit system.  I have
> consumerd's build for both 32-bit and 64-bits (followed
> http://lttng.org/docs/#doc-instrumenting-32-bit-app-on-64-bit-system)
>
> I'm seeing problem in reading 32-bit app traces, although it is logging
> something and logfile size in lttng-traces/ is increasing.
> I have compiled same app for 64-bit and it works fine.
>
> One more point here is that, this happens only when relaying traces. Without
> using relayd and by using local tracing i dont see any issues.
>
> Attached are the logs from 32-bit and 64-bit app's. There sizes are same
> except the files in index/
>
> I'm using 2.4.1 lttng and tried 1.2.0 and 1.2.1 version of babeltrace.
>
> Can anyone please tell me how can i avoid this problem.
>
> Thanks,
> Anand Neeli
>
>
> _______________________________________________
> 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