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

Anand Neeli anand.neeli at gmail.com
Thu Nov 27 06:31:13 EST 2014


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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20141127/c36c0d9b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logtrace32-6965-20141127-023258.tar.gz
Type: application/x-gzip
Size: 2996 bytes
Desc: not available
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20141127/c36c0d9b/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logtrace64-6970-20141127-023301.tar.gz
Type: application/x-gzip
Size: 3112 bytes
Desc: not available
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20141127/c36c0d9b/attachment-0001.bin>


More information about the lttng-dev mailing list