[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[ptp-user] Re: Eclipse Behaving Poorly When Remote Machine is Taken Off-line
|
Here is some additional information concerning the issue reported. To try to resolve the
remote server issues and return to local development, I've attempted to remove these features
from my installation of Eclipse. To do this, I've "uninstalled" the RSE, RDT, and PTP features
in Eclipse 3.4 using the About->Configuration->Uninstall feature. I then restarted Eclipse.
This restored the ability to use CDT for debugging as before although the break-point menu
had options for both Parallel Breakpoint and the usual Breakpoint. I re-installed all of the
components in order CDT 6.0.2, RSE 3.1.1, PTP 3.0. To allow rdt to fully install, I uninstalled the .
..cdt.testing.feature plug-in, which seemed to give a conflict. Now when I attempt to
debug the C program using the Parallel Application feature the following error is
obtained (flag for stopping in main()) has been set:
"Could not open the editor: Editor could not be initialized."
more details are provided in the blue tab:
"1 main() Main.c:34 45b15b "
the details are:
java.lang.NullPointerException
at org.eclipse.cdt.internal.ui.editor.CEditor.updateScalabilityMode(CEditor.java:1399)
at org.eclipse.cdt.internal.ui.editor.CEditor.doSetInput(CEditor.java:1346)
at org.eclipse.ui.texteditor.AbstractTextEditor$19.run(AbstractTextEditor.java:3115)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:759)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:756)
at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2579)
at org.eclipse.ui.texteditor.AbstractTextEditor.internalInit(AbstractTextEditor.java:3133)
at org.eclipse.ui.texteditor.AbstractTextEditor.init(AbstractTextEditor.java:3160)
at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:798)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:644)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:286)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2857)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2762)
at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2754)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2705)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2701)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2685)
at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility$1.run(SourceLookupFacility.java:352)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.openEditor(SourceLookupFacility.java:362)
at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.openEditor(SourceLookupFacility.java:287)
at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.display(SourceLookupFacility.java:219)
at org.eclipse.debug.ui.DebugUITools.displaySource(DebugUITools.java:792)
at org.eclipse.debug.internal.ui.elements.adapters.StackFrameSourceDisplayAdapter$SourceDisplayJob.runInUIThread(StackFrameSourceDisplayAdapter.java:155)
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:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
This seems to indicate the C editor is not able to launch or find the file. However,
the breakpoint functionality seems to work fine when opening the file. Also,
as mentioned the debugger works fine for this installation when in debugging
using a Debug Configuration in the C/C++ Application more.
Well, I really would like to use PTP for my programming and development. I've really
enjoyed using Eclipse for my C/C++ development work and having the additional
functionality would be really
valuable.to debug parallel programs using Open MPI
and Open MP.
Thanks in advance for help.
-- PA
P.S. The project on which I am working is a large-scale scientific computing code for fluid dynamics.
I ultimately would like to do Open MPI, and Open MP programming / debugging using
PTP and probably would be happy using it only in the "local mode". I think PTP would be
ideal for debugging the prototype codes on a workstation before deployment to a large cluster.
On Sun, Mar 21, 2010 at 3:14 PM, Icosohedron
<polyhedronlambda@xxxxxxxxx> wrote:
The Eclipse interface for CDT using Remote System Explorer hangs
when remote computers are taken off-line. This occurs even when trying
to use local projects which do not make any direct use of the remote
systems features. Basically, when attempting to setup a new debugger
launcher the systems seems to search for each remote machine
previously registered with Eclipse. After asking for log-in password
and a long time-out, Eclipse reports an error message about "Daemon
not launched".
Is there a way to delete the remote machine from the registry for
the Remote System Explorer? I've removed the username/password
pair and have not launched any of the resources managers, but the
problem persists. This is really frustrating, since this basically
breaks my install of Eclipse for use for local development.
This occurred for PTP 3.0, RSE 3.1.1, CDT 6.0.2.
Thanks in advance for help.
-- PA
