Target Manager perspective error


I get the following when opening the Target MAnagement perspective on a fresh install of DS:

	at java.util.HashMap.get(Unknown Source)
	at org.eclipse.ui.part.PageBookView.getPageRec(
	at org.eclipse.ui.part.PageBookView.partActivated(
	at org.eclipse.ui.internal.ViewReference.createPartHelper(
	at org.eclipse.ui.internal.ViewReference.createPart(
	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(
	at org.eclipse.ui.internal.Perspective.showView(
	at org.eclipse.ui.internal.WorkbenchPage.busyShowView(
	at org.eclipse.ui.internal.WorkbenchPage$
	at org.eclipse.swt.custom.BusyIndicator.showWhile(
	at org.eclipse.ui.internal.WorkbenchPage.showView(
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(
	at org.eclipse.swt.widgets.Display.runAsyncMessages(
	at org.eclipse.swt.widgets.Display.readAndDispatch(
	at org.eclipse.ui.internal.Workbench.runEventLoop(
	at org.eclipse.ui.internal.Workbench.runUI(
	at org.eclipse.ui.internal.Workbench.access$4(
	at org.eclipse.ui.internal.Workbench$
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(
	at com.wavecom.openat.ide.Application.start(
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(
	at org.eclipse.equinox.launcher.Main.basicRun(

Anybody seen this?


Solved it!

I did not have the USB-Serial Port driver installed on my new laptop. Since this machine doesn’t have any hard serial ports, that meant Developer Studio couldn’t find any serial ports. Apparently this caused a big problem.

I installed the driver for my USB-Serial port adapter, restarted Developer Studio, and everything functioned normally.

Sierra Devs: This should be entered as a UI bug. If Developer Studio can’t locate any serial ports, it should probably warn the user instead. The Null Pointer Exception traces made it appear the installation was corrupt.


Already known issue: DS will indeed behave quite bad if there is no serial port at all…
Planned for fix in next release.


Just as an aside:

I know laptops haven’t had external COM ports for years, but they’ve generally had an internal modem that appears as a COM port - is that now also on the way out?

(wouldn’t surprise me - who uses dial-up modems these days?!)


Yeah, this new laptop lacks a modem (it still has the plastic cutout where one would potentially have been installed). I guess the days of the modem are officially behind us.