Bug 11838 - Automatic Cross GDB only works before running the first debug session.
Summary: Automatic Cross GDB only works before running the first debug session.
Status: CLOSED OBSOLETE
Alias: None
Product: Eclipse Plugin
Classification: Yocto Project Subprojects
Component: eclipse-plugin (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 4.99
Assignee: Chin Huat Ang
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-07-26 13:12 UTC by b.turner
Modified: 2019-08-29 15:17 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
Image of first Yocto Autotools project created with working GDB debug settings automatically applied. (450.98 KB, image/png)
2017-10-24 23:13 UTC, b.turner
no flags Details
Image of second Yocto Autotools project created with GDB debug settings not automatically applied. (437.63 KB, image/png)
2017-10-24 23:14 UTC, b.turner
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description b.turner 2017-07-26 13:12:24 UTC
Automatic population of the GDB settings for a new Yocto Autotools C++ project only happens as long as a debug session has not yet been run.

Once a project is debugged, any subsequently created projects are not automatically configured and instead contain the defaults:

GDB Debugger: gdb
GDB command file: .gdbinit

Instead of the correct:

GDB Debugger: <path_to_toolchain_gdb>
GDB command file: <path_to_project_gdbinit_file>

Possibly related:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=192
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7550
Comment 1 brian avery 2017-08-23 21:28:50 UTC
Failed to replicate with YP 2.3 releases (plugin,toolchain and sysroots) for qemux86 on both neon.3 (4.6.3) and mars.2 (4.5.2). 

The relevant entries should (and do for me) appear in workspace/<proj_name>/<proj_name>_gdb_i586-poky-linux.launch

or whatever architecture you are using instead of i586.

I'll close this now as I can't replicate it, but you can reopen if you have more information.

In Run->DebugConfigurations, under C/C++ Remote Application, you should see and be able to choose from a list of <proj_nam>_gdb_i586-poky-linux.
Comment 2 b.turner 2017-10-24 23:13:32 UTC
Created attachment 4097 [details]
Image of first Yocto Autotools project created with working GDB debug settings automatically applied.
Comment 3 b.turner 2017-10-24 23:14:26 UTC
Created attachment 4098 [details]
Image of second Yocto Autotools project created with GDB debug settings not automatically applied.
Comment 4 b.turner 2017-10-24 23:18:39 UTC
I am still getting the described behavior.

After a complete re-installation of the development environment I still only have GDB debug settings applied to the first project I create in a workspace, but not to any subsequently created projects, which must be done manually.
This happens for both qemuarm and qemuarm64 builds I have done.

I have followed the Yocto guides for installing the build environment and eclipse and additional software, and I have added and installed the 2.3.2 (latest I can see) version of the plugin.

See the attachments for images of the observed behavior.
Comment 5 brian avery 2017-12-08 22:14:54 UTC
Moving to Chin Huat.

I could not replicate this, but the reporter is seeing this repeatedly.  Maybe you can replicate it?
Comment 6 Armin Kuster 2019-08-29 15:15:59 UTC
Eclipse got dropped from project support.
Comment 7 Armin Kuster 2019-08-29 15:17:16 UTC
closing