Different *.so content in recipe and rootfs

Different *.so content in recipe and rootfs

[Евгений Астафьев]

[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]

 Hi,

Yocto 2.0

I have a recipe qtbase.

RECIPE SIDE:
File /packages-split/qtbase/usr/lib/libQt5Core.so.5.5.1
Size: 5186760
Time: 01:21
 
ROOTFS SIDE:
File /usr/lib/libQt5Core.so.5.5.1
Size: 5206080
Time: 01:21

The SDK constructed by -c populate_sdk has same version of file as a recipe side has.
Actually I have no file with size 5200680 anywhere in my /tmp dir. The only place it exists - rootfs image. 
 
I have many such differencies, including libc.

The image works. Qt works. Local debugging in a device console works.
Remote debugging fails. The debugger says I have different versions of libs in my SDK's sysroot and the device.

If I view the files in MC's viewer - it shows the same function names, but different addresses.

If I put the file libQt5Core.so.5.5.1 from the recipe to rootfs manually - image still works. Remote debugger reports no errors.

But I still want to clear out what's going on and how to make debuggable image w.o. hand manipulations.

BTW I did a full rebuild of the image. No success, libs are still different

Any help is appreciated.

Eugene

[-- Attachment #2: Type: text/html, Size: 1231 bytes --]

Re: Different *.so content in recipe and rootfs

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]

On Fri, Dec 18, 2015 at 01:35:24PM +0300, Евгений Астафьев wrote:
>  Hi,
> 
> Yocto 2.0
> 
> I have a recipe qtbase.
> 
> RECIPE SIDE:
> File /packages-split/qtbase/usr/lib/libQt5Core.so.5.5.1
> Size: 5186760
> Time: 01:21
>  
> ROOTFS SIDE:
> File /usr/lib/libQt5Core.so.5.5.1
> Size: 5206080
> Time: 01:21

Do you happen to have prelink enabled for your image?

> The SDK constructed by -c populate_sdk has same version of file as a recipe side has.
> Actually I have no file with size 5200680 anywhere in my /tmp dir. The only place it exists - rootfs image. 
>  
> I have many such differencies, including libc.
> 
> The image works. Qt works. Local debugging in a device console works.
> Remote debugging fails. The debugger says I have different versions of libs in my SDK's sysroot and the device.
> 
> If I view the files in MC's viewer - it shows the same function names, but different addresses.
> 
> If I put the file libQt5Core.so.5.5.1 from the recipe to rootfs manually - image still works. Remote debugger reports no errors.
> 
> But I still want to clear out what's going on and how to make debuggable image w.o. hand manipulations.
> 
> BTW I did a full rebuild of the image. No success, libs are still different
> 
> Any help is appreciated.
> 
> Eugene

> -- 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

Re: Different *.so content in recipe and rootfs

[Евгений Астафьев]

[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]

 Yes, I have buildstats, image-mklibs, image-prelink



>Пятница, 18 декабря 2015, 14:07 +01:00 от Martin Jansa <martin.jansa@gmail.com>:
>
>On Fri, Dec 18, 2015 at 01:35:24PM +0300, Евгений Астафьев wrote:
>>  Hi,
>> 
>> Yocto 2.0
>> 
>> I have a recipe qtbase.
>> 
>> RECIPE SIDE:
>> File /packages-split/qtbase/usr/lib/libQt5Core.so.5.5.1
>> Size: 5186760
>> Time: 01:21
>>  
>> ROOTFS SIDE:
>> File /usr/lib/libQt5Core.so.5.5.1
>> Size: 5206080
>> Time: 01:21
>
>Do you happen to have prelink enabled for your image?
>
>> The SDK constructed by -c populate_sdk has same version of file as a recipe side has.
>> Actually I have no file with size 5200680 anywhere in my /tmp dir. The only place it exists - rootfs image. 
>>  
>> I have many such differencies, including libc.
>> 
>> The image works. Qt works. Local debugging in a device console works.
>> Remote debugging fails. The debugger says I have different versions of libs in my SDK's sysroot and the device.
>> 
>> If I view the files in MC's viewer - it shows the same function names, but different addresses.
>> 
>> If I put the file libQt5Core.so.5.5.1 from the recipe to rootfs manually - image still works. Remote debugger reports no errors.
>> 
>> But I still want to clear out what's going on and how to make debuggable image w.o. hand manipulations.
>> 
>> BTW I did a full rebuild of the image. No success, libs are still different
>> 
>> Any help is appreciated.
>> 
>> Eugene
>
>> -- 
>> _______________________________________________
>> yocto mailing list
>>  yocto@yoctoproject.org
>>  https://lists.yoctoproject.org/listinfo/yocto
>
>
>-- 
>Martin 'JaMa' Jansa     jabber:  Martin.Jansa@gmail.com


[-- Attachment #2: Type: text/html, Size: 3856 bytes --]

Re: Different *.so content in recipe and rootfs

[Евгений Астафьев]

[-- Attachment #1: Type: text/plain, Size: 2775 bytes --]

 Here is debugger error log

Process /opt/untitled/bin/untitled created; pid = 662
.dynamic section for "/opt/poky/2.0/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi/usr/lib/libstdc++.so.6" is not at the expected address (wrong library or version mismatch?)
.dynamic section for "/opt/poky/2.0/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi/lib/libc.so.6" is not at the expected address (wrong library or version mismatch?)
.dynamic section for "/opt/poky/2.0/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi/lib/libpthread.so.0" is not at the expected address (wrong library or version mismatch?)
.dynamic section for "/opt/poky/2.0/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi/lib/libm.so.6" is not at the expected address (wrong library or version mismatch?)
.dynamic section for "/opt/poky/2.0/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi/lib/librt.so.1" is not at the expected address (wrong library or version mismatch?)
File "/opt/poky/2.0/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi/usr/lib/libstdc++.so.6.0.21-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:


>Пятница, 18 декабря 2015, 14:07 +01:00 от Martin Jansa <martin.jansa@gmail.com>:
>
>On Fri, Dec 18, 2015 at 01:35:24PM +0300, Евгений Астафьев wrote:
>>  Hi,
>> 
>> Yocto 2.0
>> 
>> I have a recipe qtbase.
>> 
>> RECIPE SIDE:
>> File /packages-split/qtbase/usr/lib/libQt5Core.so.5.5.1
>> Size: 5186760
>> Time: 01:21
>>  
>> ROOTFS SIDE:
>> File /usr/lib/libQt5Core.so.5.5.1
>> Size: 5206080
>> Time: 01:21
>
>Do you happen to have prelink enabled for your image?
>
>> The SDK constructed by -c populate_sdk has same version of file as a recipe side has.
>> Actually I have no file with size 5200680 anywhere in my /tmp dir. The only place it exists - rootfs image. 
>>  
>> I have many such differencies, including libc.
>> 
>> The image works. Qt works. Local debugging in a device console works.
>> Remote debugging fails. The debugger says I have different versions of libs in my SDK's sysroot and the device.
>> 
>> If I view the files in MC's viewer - it shows the same function names, but different addresses.
>> 
>> If I put the file libQt5Core.so.5.5.1 from the recipe to rootfs manually - image still works. Remote debugger reports no errors.
>> 
>> But I still want to clear out what's going on and how to make debuggable image w.o. hand manipulations.
>> 
>> BTW I did a full rebuild of the image. No success, libs are still different
>> 
>> Any help is appreciated.
>> 
>> Eugene
>
>> -- 
>> _______________________________________________
>> yocto mailing list
>>  yocto@yoctoproject.org
>>  https://lists.yoctoproject.org/listinfo/yocto
>
>
>-- 
>Martin 'JaMa' Jansa     jabber:  Martin.Jansa@gmail.com


[-- Attachment #2: Type: text/html, Size: 4765 bytes --]