Bug 7550

Summary: Using "Debugger" combo resets "GDB debugger" and "GDB command file" fields
Product: [Yocto Project Subprojects] Eclipse Plugin Reporter: Joshua Lock <joshuagloe>
Component: eclipse-pluginAssignee: Todor Minchev <todor.minchev>
Status: VERIFIED NOTABUG QA Contact: Alexandru Roman <alexandru.costinx.roman>
Severity: normal    
Priority: Medium CC: alexandru.costinx.roman, bogdanx.a.voiculescu, ioanax.grigoropol, yp.ep.watcher, yp.watcher
Version: 1.7.1   
Target Milestone: 1.9   
Hardware: x86   
OS: Multiple   
See Also: https://bugzilla.yoctoproject.org/show_bug.cgi?id=11838
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Joshua Lock 2015-03-31 13:26:52 UTC 
I'm trying to test the Eclipse plugin with Dizzy by using the skeletal projects provided by the Yocto Eclipse Plugin.

When editing Debug Configurations after selecting the "Debug As" menu option I switch to the "Debugger" tab of the "C/C++ Remote Application" view and click on the "Debugger" combo to see what options are available.
Seeing that the only option is the one already selected I click on it to dismiss close the combo and see that both the "GDB Debugger" and "GDB command file" entries in "Debugger Options" are reset to "gdb" and ".gdbinit" respectively, rather than the appropriate Yocto entries that were populated before interacting with the combo box. This is rather alarming.

Fortunately the "Revert" button resets the fields appropriately, but that took me some time to find...

ADT Plug-in: 1.4.0 (installed from the 1.7.1/kepler software installation site)
Eclipse IDE: Kepler SR 2 (installed from a tarball downloaded from eclipse.org)
Poky: Dizzy HEAD (running the dizzy branch from git with a HEAD of ec75238f6cc2d2d8d40e0268f6d2acc070cbe9a4)
Toolchain: bitbake -c populate_sdk core-image-sato-sdk
OS: Ubuntu 14.10 x86_64
Comment 1 Todor Minchev 2015-04-23 08:57:44 UTC 
This is not specific to the Yocto plugin, the Eclipse gdb remote debugger automatically sets the defaults for a given machine interface option. I am not sure if it is a bug, because the defaults are also valid and there is a revert option.
Comment 2 Alexandru Roman 2015-08-31 10:51:57 UTC 
Verify on mars-master: 05ba7b6791083a70c78366f9737e27d9dd25d08b