In older CDT versions, the Problems view would show the results of
invoking a make target. In 4.0 RC0, this doesn't appear to be
happening. Regular build output appears in the Problems view, but make
targets only appear to affect the console. This, you might imagine,
makes fixing errors a lot more tedious.
All of the error parsers are enabled in my project settings.
Possibly related, the first time I click on C/C++ Build / Settings, I
get an "unknown error." I think the associated log message is:
!ENTRY org.eclipse.ui 4 0 2007-05-03 12:52:56.134
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.ArrayIndexOutOfBoundsException: 7
at
org.eclipse.cdt.ui.newui.BinaryParsTab.updateData(BinaryParsTab.java:186)
at
org.eclipse.cdt.ui.newui.AbstractCPropertyTab.setVisible(AbstractCPropertyTab.java:198)
at
org.eclipse.cdt.ui.newui.BinaryParsTab.setVisible(BinaryParsTab.java:166)
at
org.eclipse.cdt.ui.newui.AbstractCPropertyTab.handleTabEvent(AbstractCPropertyTab.java:500)
at
org.eclipse.cdt.ui.newui.AbstractPage$4.widgetSelected(AbstractPage.java:314)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1097)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3256)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2923)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
at org.eclipse.jface.window.Window.open(Window.java:796)
at
org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:156)
at
org.eclipse.ui.internal.ide.actions.ProjectPropertyDialogAction.run(ProjectPropertyDialogAction.java:77)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1097)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3256)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2923)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2337)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2301)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2176)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:463)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:458)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:101)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:146)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:356)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:171)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:476)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:416)
at org.eclipse.equinox.launcher.Main.run(Main.java:1141)
Any ideas?
Other than this, and a few typical nav issues, CDT 4.0 RC0 is looking
pretty good.