Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Upcoming release dates (was CDT8.4 + 8.5 - all debug buttons become disabled)

On 03 Dec 2014, at 19:11, Mikhail Khodjaiants <mikhailkhod@xxxxxxxxxxxxxx> wrote:

> Is there anything in the log file?

nope.

I did two tests with my GDB SEGGER J-Link plug-in, first in an existing workspace, then in a fresh workspace, and each time the first launch has disabled buttons, and after a restart the buttons are visible.

in both cases there are no special exceptions for the first launch. 

to be fair, there are two stack overflow exceptions, but they appear with each Eclipse start (this is another problem with Luna).

!ENTRY org.eclipse.e4.ui.workbench.renderers.swt 4 2 2014-12-03 20:38:48.901
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.e4.ui.workbench.renderers.swt".
!STACK 0
org.eclipse.e4.core.di.InjectionException: java.lang.StackOverflowError
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:62)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
	at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.setEnabled(HandlerServiceHandler.java:77)
	at org.eclipse.core.commands.Command.setEnabled(Command.java:886)
	at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.canExecute(HandlerServiceImpl.java:179)
	at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.canExecuteItem(HandledContributionItem.java:839)
	at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$1(HandledContributionItem.java:828)
	at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$3.run(HandledContributionItem.java:165)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
...

!ENTRY org.eclipse.e4.ui.workbench 4 0 2014-12-03 20:38:48.923
!MESSAGE Internal error during tool item enablement updating, this is only logged once per tool item.
!STACK 0
org.eclipse.e4.core.di.InjectionException: java.lang.StackOverflowError
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:62)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
	at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.setEnabled(HandlerServiceHandler.java:77)
	at org.eclipse.core.commands.Command.setEnabled(Command.java:886)
	at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.canExecute(HandlerServiceImpl.java:179)
	at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.canExecuteItem(HandledContributionItem.java:839)
	at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$1(HandledContributionItem.java:828)
	at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$3.run(HandledContributionItem.java:165)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
...


so, if Derek wants to trace this, I think it is quite easy to reproduce: install the GNU ARM Eclipse plug-ins, create an Cortex-M project using the defaults, build the Debug configuration, create a J-Link launch and debug it on a physical board. the first time you launch it, the buttons are disabled. you want to reproduce it again, create a new launcher.

please contact me by email for more details, if needed.


regards,

Liviu




Back to the top