| Summary: | Support multi-image debugging | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Eclipse Plugin | Reporter: | Todor Minchev <todor.minchev> |
| Component: | eclipse-plugin | Assignee: | brian avery <brian.avery> |
| Status: | RESOLVED INVALID | QA Contact: | Valentin Hangan <valentinx.hangan> |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | ioanax.grigoropol, mober.at, randy.macleod, sgw, todor.minchev, valentinx.hangan, yp.ep.watcher, yp.watcher |
| Version: | 1.9 | ||
| Target Milestone: | 2.3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Todor Minchev
2015-05-29 09:30:34 UTC
What do you mean by "target image" in that case, the executable image or the SDK (QEMU/Platform) image ? I meant that the user should be able to easily switch between different QEMU images where they can run or debug their application. Interesting, thanks ! Would you mind letting me know what kind of approach you are planning for this ? We've been supporting multiple SDKs for debugging in our Yocto based Eclipse Workbench since many years, and if you add that support now I'd like to see if/how we can integrate our approach. FYI, our current approach uses Eclipse TCF/Target Explorer. A QEMU instance is modeled as a Target Explorer connection (with path to SDK, as well as QEMU options, as properties). "Connecting" the connection can launch the QEMU, or attach to an already running QEMU that was launched on command-line. Once connected, TCF/Target Explorer manages the debug launches (run, or attach, either to a TCF debug agent or to gdbserver). Since we can also make different connections (TCF or SSH) to a set of external tools -> Qemu instances, we can accomplish the multi-image debug by making a diff debug configuration for each connection and just picking that one to debug. Closing. |