| Summary: | Which host/cross GDB to use? | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Anjuta Plugin | Reporter: | Gary Thomas <gary> |
| Component: | anjuta-plugin | Assignee: | Joshua Lock - Disabled <josh> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | High | CC: | josh, liping.ke, yp.ap.watcher, yp.watcher |
| Version: | 0.9 | ||
| Target Milestone: | 0.9 M1 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Gary Thomas
2010-04-01 12:39:05 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? 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 :-( (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 *** |