Bug 346

Summary: arm gdb poky_tree mode client and server communication fails
Product: [Build System, Metadata & Runtime] OE-Core Reporter: liping Ke <liping.ke>
Component: coreAssignee: Saul Wold <sgw>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: jessica.zhang, kevin.tian, lianhao.lu, meta.mr.watcher, meta.watcher, sgw
Version: 0.9   
Target Milestone: 0.9 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Program Management Documentation change: ---

Description liping Ke 2010-09-20 20:29:21 UTC
Seems this is a version mis-match problem (this error happens under command line too).
If I choose poky tree mode, when gdb server and gdb client begin cooperate to debug, the client will report
"Remote 'g' packet reply is too long.

I meet this problem only on ARM currently. (Error is pasted below). Strange thing is that if I choose /opt/poky/ sdk mode, everything is fine.

I did not compare the two files very well, but the two armXXX-gdb files size differs a lot!



emote 'g' packet reply is too long: 00000000f69ea9be0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000109ea9be00000000e007004010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Remote 'g' packet reply is too long: 00000000f69ea9be0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000109ea9be00000000e007004010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Remote 'g' packet reply is too long: 00000000f69ea9be0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000109ea9be00000000e007004010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Comment 1 liping Ke 2010-09-20 22:53:39 UTC
paste two different file size log



lke@lke-nhm:~/Desktop$ ll /media/poky/new_poky.git/build_arm/tmp/sysroots/i686-linux/usr/bin/armv5te-poky-linux-gnueabi/arm-poky-linux-gnueabi-gdb
-rwxr-xr-x 1 lke lke 3145107 2010-09-19 07:53 /media/poky/new_poky.git/build_arm/tmp/sysroots/i686-linux/usr/bin/armv5te-poky-linux-gnueabi/arm-poky-linux-gnueabi-gdb*
lke@lke-nhm:~/Desktop$ ll /opt/poky/sysroots/i586-pokysdk-linux/usr/bin/armv5te-poky-linux-gnueabi/arm-poky-linux-gnueabi-gdb
-rwxr-xr-x 1 lke lke 2557772 2010-09-19 08:20 /opt/poky/sysroots/i586-pokysdk-linux/usr/bin/armv5te-poky-linux-gnueabi/arm-poky-linux-gnueabi-gdb*
Comment 2 Saul Wold 2010-09-29 17:42:09 UTC
I was able to reproduce this finally! I think the problem is how the two gdbs are built.
Comment 3 Saul Wold 2010-09-30 12:16:03 UTC
Problem was cross gdb for the poky tree was missing a --with-expat configuration
Comment 5 Jessica 2010-09-30 16:11:16 UTC
Verified with the latest build from poky-master, the cross gdb debugging worked fine against program runnint in qemu-arm