Bug 384715 - SDM debugger generates an error message
Summary: SDM debugger generates an error message
Status: NEW
Alias: None
Product: PTP
Classification: Tools
Component: Debug SDM (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2012-07-10 08:07 EDT by Dheeraj Chahal CLA
Modified: 2014-06-09 15:53 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dheeraj Chahal CLA 2012-07-10 08:07:05 EDT
Build Identifier: Eclipse build level : Eclipse Platform	4.2.0.I20120608-1400,	

Eclipse build level :     Eclipse Platform	4.2.0.I20120608-1400	
PTP build level :    Parallel Tools Platform (PTP) End-User Runtime	6.0.0.201206252139

Client platform  : Windows XP / Windows 7

Server node : x86/P7 Linux (RHEL 6.2)
Application programing language : C
Compiler used : mpcc




Reproducible: Always

Steps to Reproduce:
Steps :
1. Create a synchronized c/c++ project.
2. Build project.
3. Debug binary using debug configuration.
4. New window pops up with error message: 

   An internal error has occurred.
   java.lang.NullPointerException

5. If we accept this error mesage by clicking OK, we can proceed with SDM debugger and set the break points, do stepping etc, 
until the program exits normally.



The Error log mentioned in step 4 is as below:

java.lang.NullPointerException
	at org.eclipse.jface.viewers.TreeViewer.getParentElement(TreeViewer.java:602)
	at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand(AbstractTreeViewer.java:1641)
	at org.eclipse.jface.viewers.AbstractTreeViewer.setExpandedState(AbstractTreeViewer.java:2497)
	at org.eclipse.ptp.debug.ui.views.ParallelDebugView$3.runInUIThread(ParallelDebugView.java:594)
	at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
	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:353)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
	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:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
Comment 1 Greg Watson CLA 2014-06-09 15:53:19 EDT
Needs to be tested for Luna.