Different *.so content in recipe and rootfs
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
Quoted 6 lines · Евгений Астафьев
Hi,
Yocto 2.0
I have a recipe qtbase.
Quoted 9 lines
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?
Quoted 25 lines
The SDK constructed by -c
populate_sdkhas 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
Signature · 4 lines
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Yes, I have buildstats, image-mklibs, image-prelink
Quoted 50 lines
Пятница, 18 декабря 2015, 14:07 +01:00 от Martin Jansa <[email protected]>:
Quoted 6 lines · Евгений Астафьев
Hi,
Yocto 2.0
I have a recipe qtbase.
Quoted 9 lines
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:21Do you happen to have prelink enabled for your image?
Quoted 25 lines
The SDK constructed by -c
populate_sdkhas 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
Signature · 4 lines
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yoctoSignature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
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:
Quoted 50 lines
Пятница, 18 декабря 2015, 14:07 +01:00 от Martin Jansa <[email protected]>:
Quoted 6 lines · Евгений Астафьев
Hi,
Yocto 2.0
I have a recipe qtbase.
Quoted 9 lines
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:21Do you happen to have prelink enabled for your image?
Quoted 25 lines
The SDK constructed by -c
populate_sdkhas 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
Signature · 4 lines
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yoctoSignature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]