Bug 88 - Which host/cross GDB to use?
Summary: Which host/cross GDB to use?
Status: RESOLVED DUPLICATE of bug 86
Alias: None
Product: Anjuta Plugin
Classification: Yocto Project Subprojects
Component: anjuta-plugin (show other bugs)
Version: 0.9
Hardware: All Multiple
: High normal
Target Milestone: 0.9 M1
Assignee: Joshua Lock - Disabled
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-04-01 12:39 UTC by Gary Thomas
Modified: 2010-12-21 05:58 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Thomas 2010-04-01 12:39:05 UTC
There seems to be no way to specify which host [cross] GDB to use.

n.b. if the plugin is expecting to use <target-triplet>-gdb, this is
not installed with the SDK (perhaps it should be)
Comment 1 Joshua Lock - Disabled 2010-04-16 15:46:45 UTC
Needs investigation, does the plugin just default to using a certain gdb which we then need to ensure is there before running the remote debugger? 

From plugin.c:691 looks like we're trying building the executable name from the sdk root and the host triplet, have recent poky changes broken this?
Comment 2 Gary Thomas 2010-04-16 15:57:56 UTC
The plugin assumes <target-triplet>-gdb

This is neither built nor installed when using meta-toolchain-sdk
It can be built and manually installed via gdb-cross

Sadly, if the gdb executable is not available, the anjuta framework
does not report any error when creating the gdb [host] controller
and the plugin simply sits and waits for the initial connection :-(
Comment 3 liping Ke 2010-05-21 03:59:42 UTC
(In reply to comment #2)
> The plugin assumes <target-triplet>-gdb
> 
> This is neither built nor installed when using meta-toolchain-sdk
> It can be built and manually installed via gdb-cross
> 
> Sadly, if the gdb executable is not available, the anjuta framework
> does not report any error when creating the gdb [host] controller
> and the plugin simply sits and waits for the initial connection :-(

> 
Hi, Gary
I did build this cross gdb with SDK tools together.it is under the folder of build/tmp/deploy/sdk. And you should untar this tarball to /, so under /usr/local/poky/eabi-glibc/bin, you will see XXX-poky-linux-gdb. (xxx-poky-linux is the tool chain triplet you are setting).
Yes, it's true when the cross gdb does not exist, the terminal will have problem. I mark this problem as a repeated bug as bug 2060 and trace all those terminal related bugs there.

Thanks & Regards,
criping



*** This bug has been marked as a duplicate of bug 2060 ***