Bug 325

Summary: the arm gdb tool name convention is not target-triplet + "-gdb"
Product: [Build System, Metadata & Runtime] OE-Core Reporter: liping Ke <liping.ke>
Component: devtools / tool chainAssignee: Richard Purdie <richard.purdie>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: jessica.zhang, kevin.tian, liping.ke, 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-14 02:34:41 UTC
the arm gdb tool name convention is not target-triplet + "-gdb", it is not (armvte5-poky-linux-gnueabi-gdb), but (arm-poky-linux-gnueabi-gdb) instead. (triplet is armvte5-poky-linux-gnueabi). Maybe Josh could help us.
Otherwise, we have no way to know the gdb-cmd-name and fill-in the cdt-remote-gdb-editbox in ahead.

Josh, any comments about this?

Thanks& Regards,
criping
Comment 1 Saul Wold 2010-09-15 14:58:54 UTC
Prefix is correct, but we may need to export TARGET_ARCH also to enable you to find right files.
Comment 2 Jessica 2010-09-16 00:09:51 UTC
To make things less error prone that we have to figure out exact gdb tools name through code, can we add an entry in the environment script called GDB and spell out the name, we are currently already doing it for CC and CXX.
Comment 3 Richard Purdie 2010-09-16 07:31:10 UTC
I've added:
http://git.pokylinux.org/cgit.cgi/poky/commit/?id=f47ae202afd6ef9aa600fed4c1d096dfb7613286
 which should give you the option of using TARGET_PREFIX or the GDB variable directly.
Comment 4 liping Ke 2010-09-18 19:06:51 UTC
I saw the export GDB vars with both arm and i586 arch with tip of code. (d1ff9aa4f, RP, Sep. 16, 2010) 
It works fine!