- This topic has 9 replies, 4 voices, and was last updated 13 years, 2 months ago by
.
-
Posts
-
If I try to launch the a CDT debug session I get the following error:
java.lang.IllegalArgumentException at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.getBundles(PackageAdminImpl.java:571) at org.eclipse.core.internal.runtime.InternalPlatform.getBundle(InternalPlatform.java:181) at org.eclipse.core.runtime.Platform.getBundle(Platform.java:1416) at org.springframework.ide.eclipse.core.BundleStateLocationVariableResolver.resolveValue(BundleStateLocationVariableResolver.java:32) at org.eclipse.core.internal.variables.DynamicVariable.getValue(DynamicVariable.java:54) at org.eclipse.cdt.internal.core.cdtvariables.EclipseVariablesVariableSupplier$EclipseVarMacro.loadValue(EclipseVariablesVariableSupplier.java:103) at org.eclipse.cdt.internal.core.cdtvariables.EclipseVariablesVariableSupplier$EclipseVarMacro.getStringValue(EclipseVariablesVariableSupplier.java:90) at org.eclipse.cdt.dsf.gdb.launching.LaunchUtils.getLaunchEnvironment(LaunchUtils.java:389) at org.eclipse.cdt.dsf.gdb.launching.LaunchUtils.getGDBVersion(LaunchUtils.java:281) at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.getGDBVersion(GdbLaunchDelegate.java:243) at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:129) at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:83) at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:72) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:923) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1126) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)The default launcher is set to “GDB (DSF) Create Process Launcher”.
I’m running the latest Myeclipse (9.1) IDE on a 64-bit linux machine. Any suggestions on how to fix?
ccrotty,
Sorry that you are running into this issue. Let me clarify that MyEclipse doesn’t provide an integrated support for CDT. Having said that there are users who have successfully integrated 3rd party plugins with MyEclipse profile.
Can you answer some more questions for me to replicate the issue at my end?
1) How did you install CDT plugin and which version?
2) Can you give me steps in detail on how you are trying to debug and how you set the default launcher?
3) Also share the C/C++ file which you are trying to debug.
Thanks for the help.
1) I installed the CDT using the Configuration Center, under the Pulse Catalog->Languages->Eclipse C/C++ Development tools. The installed version is 7.0.2
2) I can adjust the Launcher by going to the Debug configuration page. On the bottom of the ‘Main” tab is the ability to change the Launcher.
The ‘GDB (DSF) Create Process Launcher’ is selected by default. This is what gives me the error. If I change the Launcher to ‘Standard Create Process Launcher’ then it can launch ok.I am using the ‘Standard’ launcher now. The only unfortunate thing is this standard launcher does not have some of the conveniences like better c++ symbol mapping during code exploration.
3) The project is quite large, and I don’t think that the files have anything to do with this problem, as I believe it is some configuration problem.
ccrotty,
We are attempting to reproduce this internally. However, in the interim, I can suggest this quick fix.
If you do not use our Spring functionality, go to Help > MyEclipse Configuration Center and the Dashboard tab. Under the MyEclipse Features section, find Spring Support for MyEclipse and uncheck it. Click apply to remove the Spring functionality from MyEclipse and restart. The conflict/problem appears to be in our Spring tooling, so removing it should fix the issue for now.
Sorry for the inconvenience caused.
ccrotty,
Thank you for the details. I could replicate the issue at my end.
I have filed a PR with the dev team to investigate it further.Sorry for the inconvenience caused.
Chris,
That is odd
1) Are you still seeing exactly the same stack trace?2) If you go to Help > About > Plug-Ins – can you see the com.genuitec.eclipse.springframework and the org.springframework.ide.eclipse.core plugins (You can sort this list alphabetically by clicking the plug-in Id column)
3) Are you sure you correctly removed the Spring support? If you go to the Dashboard again, is the “Spring Support for MyEclipse” item unchecked?
1)Yes, I am seeing the same stack trace.
2) com.genuitec.eclipse.springframework in NOT there, but I do see the org.springframework.ide.eclipse.core plugin (along with 16 other org.springwork.* plugins)
3) Yes, both MyEclipse for Spring and Spring Support for MyEclipse are unchecked in the dashboard.
I have read through this post, and I am getting the same error.
Has any resolution to this issue been found?
Thank You for your time.
We will be fixing this in ME 10.0 and considering a fix for 9.1.1. In the meanwhile, I can only suggest the following workaround.
1) As described earlier, make sure you remove “Spring support for MyEclipse” from our Dashboard and apply / restart as required.
2) Shut down MyEclipse.
3) Go to <profile location>\configuration\org.eclipse.equinox.simpleconfigurator and make a backup of the bundles.info file.
Edit the bundles.info file and remove the line containing “org.springframework.ide.eclipse.core”
4) Save the file and restart MyEclipse.Notes:
a) The <profile location> is the directory containing your MyEclipse executable.
b) This is a hackish workaround which should not be a problem if you do not use our Spring features. The proposed fix will not require removal of the Spring features at all and is being tested right now.Sorry for the inconvenience caused.
