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

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

[Anand Neeli]

[-- Attachment #1.1: Type: text/plain, Size: 782 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 1091 bytes --]

[-- Attachment #2: logtrace32-6965-20141127-023258.tar.gz --]
[-- Type: application/x-gzip, Size: 2996 bytes --]

[-- Attachment #3: logtrace64-6970-20141127-023301.tar.gz --]
[-- Type: application/x-gzip, Size: 3112 bytes --]

[-- Attachment #4: Type: text/plain, Size: 155 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: not able to read 32-bit app traces running on a 64-bit system with relayd

[Jérémie Galarneau]

Hi Anand,

Would you mind testing this fix (based on master)?
https://github.com/jgalar/lttng-tools/tree/consumerd_comm_fix

Regards,
Jérémie

On Wed, Dec 3, 2014 at 5:58 PM, Jérémie Galarneau
<jeremie.galarneau@efficios.com> wrote:
> On Tue, Dec 2, 2014 at 1:10 PM, Anand Neeli <anand.neeli@gmail.com> wrote:
>> Hi Jérémie,
>> Thanks for verifying this.
>>
>> Is this a issue with relayd? or babeltrace?
>> Coz i see this only with 32-bit applications running on a 64-bit system,
>> along with relay of traces using relayd
>
> It's caused by a bug in the communication between the session and
> consumer daemons of different bitness.
> I'm working on a fix which will be back-ported to 2.4, 2.5 and 2.6.
>
> I'll keep you posted as soon as it is available.
>
> Regards,
> Jérémie
>
>>
>> Thanks,
>> Anand Neeli
>>
>> On Tue, Dec 2, 2014 at 11:03 PM, Jérémie Galarneau
>> <jeremie.galarneau@efficios.com> wrote:
>>>
>>> On Tue, Dec 2, 2014 at 8:01 AM, Anand Neeli <anand.neeli@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@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@lists.lttng.org" <lttng-dev@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@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



-- 
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: 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 1:10 PM, Anand Neeli <anand.neeli@gmail.com> wrote:
> Hi Jérémie,
> Thanks for verifying this.
>
> Is this a issue with relayd? or babeltrace?
> Coz i see this only with 32-bit applications running on a 64-bit system,
> along with relay of traces using relayd

It's caused by a bug in the communication between the session and
consumer daemons of different bitness.
I'm working on a fix which will be back-ported to 2.4, 2.5 and 2.6.

I'll keep you posted as soon as it is available.

Regards,
Jérémie

>
> Thanks,
> Anand Neeli
>
> On Tue, Dec 2, 2014 at 11:03 PM, Jérémie Galarneau
> <jeremie.galarneau@efficios.com> wrote:
>>
>> On Tue, Dec 2, 2014 at 8:01 AM, Anand Neeli <anand.neeli@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@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@lists.lttng.org" <lttng-dev@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@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

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: not able to read 32-bit app traces running on a 64-bit system with relayd

[Anand Neeli]

[-- Attachment #1.1: Type: text/plain, Size: 2424 bytes --]

Hi Jérémie,
Thanks for verifying this.

Is this a issue with relayd? or babeltrace?
Coz i see this only with 32-bit applications running on a 64-bit system,
along with relay of traces using relayd

Thanks,
Anand Neeli

On Tue, Dec 2, 2014 at 11:03 PM, Jérémie Galarneau <
jeremie.galarneau@efficios.com> wrote:

> On Tue, Dec 2, 2014 at 8:01 AM, Anand Neeli <anand.neeli@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@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@lists.lttng.org" <lttng-dev@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@lists.lttng.org
> > http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> >
>
>
>
> --
> Jérémie Galarneau
> EfficiOS Inc.
> http://www.efficios.com
>

[-- Attachment #1.2: Type: text/html, Size: 4061 bytes --]

[-- Attachment #2: Type: text/plain, Size: 155 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: 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@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@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@lists.lttng.org" <lttng-dev@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@lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>



-- 
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: not able to read 32-bit app traces running on a 64-bit system with relayd

[Anand Neeli]

[-- Attachment #1.1: Type: text/plain, Size: 1288 bytes --]

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.

Thanks,
Anand Neeli

---------- Forwarded message ----------
From: Anand Neeli <anand.neeli@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@lists.lttng.org" <lttng-dev@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

[-- Attachment #1.2: Type: text/html, Size: 2000 bytes --]

[-- Attachment #2: logtrace32-6965-20141127-023258.tar.gz --]
[-- Type: application/x-gzip, Size: 2996 bytes --]

[-- Attachment #3: logtrace64-6970-20141127-023301.tar.gz --]
[-- Type: application/x-gzip, Size: 3112 bytes --]

[-- Attachment #4: Type: text/plain, Size: 155 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev