Target Manager perspective error


#1

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

java.lang.NullPointerException
	at com.swi.tm.ui.commons.views.PortWorkbenchPart.hashCode(PortWorkbenchPart.java:35)
	at java.util.HashMap.get(Unknown Source)
	at org.eclipse.ui.part.PageBookView.getPageRec(PageBookView.java:693)
	at org.eclipse.ui.part.PageBookView.partActivated(PageBookView.java:749)
	at com.swi.tm.ui.commons.views.AbstractTMPageBookView.switchPort(AbstractTMPageBookView.java:160)
	at com.swi.tm.ui.commons.views.AbstractTMPageBookView.createPartControl(AbstractTMPageBookView.java:112)
	at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:375)
	at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:229)
	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
	at org.eclipse.ui.internal.Perspective.showView(Perspective.java:2245)
	at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1071)
	at org.eclipse.ui.internal.WorkbenchPage$20.run(WorkbenchPage.java:3822)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
	at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:3819)
	at com.swi.tm.ui.commons.ViewUtils.createViewWithSecondaryId(ViewUtils.java:44)
	at com.swi.tm.ui.commons.views.AbstractTMPageBookView$2.run(AbstractTMPageBookView.java:141)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at com.wavecom.openat.ide.Application.start(Application.java:190)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	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(Main.java:619)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1407)

Anybody seen this?


#2

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.


#3

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


#4

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?!)


#5

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.