Bug 5409 - Debug Configuration Not Created
Summary: Debug Configuration Not Created
Status: RESOLVED FIXED
Alias: None
Product: ADT
Classification: Yocto Project Subprojects
Component: adt (show other bugs)
Version: 1.5
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.5.1
Assignee: Jessica
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-10-29 14:16 UTC by Gabriel Barbu
Modified: 2013-12-27 20:25 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Debug configuration not created (106.40 KB, image/jpeg)
2013-10-29 14:16 UTC, Gabriel Barbu 		no flags Details
Native debugger shown (169.74 KB, image/jpeg)
2013-10-29 14:18 UTC, Gabriel Barbu 		no flags Details
Debugger launcher stuck (29.78 KB, image/jpeg)
2013-10-29 14:19 UTC, Gabriel Barbu 		no flags Details
Yocto Project ADT (86.61 KB, image/jpeg)
2013-10-29 14:50 UTC, Gabriel Barbu 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gabriel Barbu 2013-10-29 14:16:47 UTC 
Created attachment 1584 [details]
Debug configuration not created

Attempting to debug remotely on external hardware
as per: http://www.yoctoproject.org/docs/current/adt-manual/adt-manual.html 
and http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#adt-eclipse
and using Eclipse Juno
fails: the debug configuration is not created.

Steps/Issues:
4.2.2.4. Building the Project
=> Problems:
Description	Resource	Path	Location	Type
Missing PROG arm-poky-linux-gnueabi-mt	y_ub12_zynq_hello		-1	Configure Problem
Missing PROG arm-poky-linux-gnueabi-dlltool	y_ub12_zynq_hello		-1	Configure Problem
Missing PROG dlltool	y_ub12_zynq_hello		-1	Configure Problem

4.2.2.6. Deploying and Debugging the Application
1.	Select "Debug Configurations..." from the "Run" menu.
2.	In the left area, expand C/C++Remote Application.
=> Project specific debug configuration not created (C/C++Remote Application is empty). 
See att. Debug configuration not created

Double-clicking the C/C++Remote Application => project specific debug config is created but...

4.2.2.6. Deploying and Debugging the Application
5. Click on the "Debugger" tab to see the cross-tool debugger you are using.
=> Native debugger shown instead of proper/cross-debugger:
see: att. Native debugger shown

13. Click "Run" to bring up a login screen and login.
14. Accept the debug perspective. 
=> Debugger launcher stuck at 84%:
see att: Debugger launcher stuck
Comment 1 Gabriel Barbu 2013-10-29 14:18:38 UTC 
Created attachment 1585 [details]
Native debugger shown
Comment 2 Gabriel Barbu 2013-10-29 14:19:39 UTC 
Created attachment 1586 [details]
Debugger launcher stuck
Comment 3 Jessica 2013-10-29 14:43:47 UTC 
Hi Gabriel,

What is your toolchain and sysroot, by seeing your build project error, seems there maybe some issue with your cross environment.

Thanks,
Jessica
Comment 4 Gabriel Barbu 2013-10-29 14:50:15 UTC 
Created attachment 1587 [details]
Yocto Project ADT

Hi Jessica,
Please see toolchain and sysroot in att. Yocto_Project_ADT.
Thanks,
Gabriel
Comment 5 Jessica 2013-10-29 15:37:34 UTC 
Some follow on questions:

So this is 1.5 instead of 1.4 right? Is the same cross setup work for kepler?
Comment 6 Gabriel Barbu 2013-10-29 15:48:15 UTC 
Yes, it is yocto 1.5.

(But I thought I should enter in that field the plugin version and I got from
Eclipse > Menu > Help > About Eclipse SDK > Installation Details:
  Yocto Project ADT Plug-in	1.4.0.201310120534	org.yocto.sdk.feature.group	yoctoproject.org)
Comment 7 Jessica 2013-10-29 15:52:45 UTC 
change back to new state since more info is collected
Comment 8 Jessica 2013-10-31 23:25:24 UTC 
Hi,

One more question, how you get the toolchain, you build yourself or downloaded somewhere?
Comment 9 Gabriel Barbu 2013-11-01 09:56:28 UTC 
Hi,

I built it myself, right after building the image:
bitbake core-image-sato-sdk
bitbake meta-toolchain
Comment 10 Jessica 2013-11-15 00:44:59 UTC 
Hi Gabriel,

Is this thing only happens on Juno and Kepler is fine?
Comment 11 Gabriel Barbu 2013-11-15 13:23:53 UTC 
Hi Jessica,

We have only tested on Juno.

Meanwhile, we also found that:
- Older toolchains (from mid June) don’t have this issue while being used with the same Eclipse setup.
- Current toolchains have the issue: all architectures except x86/romley-ivb
Comment 12 mgwerder 2013-12-09 10:35:57 UTC 
I can see the same behavior with the following setup:

Eclipse Kepler SR1 (20130919-0819)
Yocto ADT plugin 1.5 for Kepler (1.4.0.201310120529, installed from downloads.yoctoproject.org/releases/eclipse-plugin/1.5/kepler)

Steps to reproduce:
- Install an SDK in a custom directory using the ADT installer from the Yocto 1.5 release.
- Install Eclipse Kepler according to the Yocto Development Manual, section "Working with Eclipse".
- Create a new Yocto C++ Autotools Project using the wizard.

The project is created, but no .launch and no .gdbinit files are created.

The same thing happens, if the Yocto project settings are applied to an existing project. The Yocto Project Console says "The Yocto Project ADT has been successfully set up for this project", though these two files are not created.

When pointing to a yocto build tree ("build system derived toolchain") with the same Eclipse version, everything works well - it only happens when pointing to an SDK that has been installed using the ADT installer ("standalone pre-built toolchain").

Thanks for any update on this.
Matthias