Progress dialog comes up, "Operation in progress...", "Upload file".
Progress just hangs at about 20%.
No errors appear in error view until operation is cancelled.
Open MPI resource manager, tunnel set to ssh port forwarding,
Parallel debugging perspective comes up.
Progress dialog comes up and completes.
Error dialog pops up: "Error on tasks:0 - Internal Error Reason: Debugger error: bad response from gdb.
The error dialog is repeated two more times.
When I go to the linux system and run gdb I get the following:
[genly@longhorn ~]$ gdb
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
(gdb)
From: "Greg Watson" <g.watson@xxxxxxxxxxxx>To: "PTP User list" <ptp-user@xxxxxxxxxxx>Sent: Monday, November 8, 2010 5:27:28 AMSubject: Re: [ptp-user] PTP debug launch hangs: Waiting for job information...When you create a new resource manager, you are able to select a number of different types (Open MPI, PBS, etc.) One of these types is "Generic Remote Launch". This resource manager will simply run an executable on a remote machine using ssh. Using this resource manager will verify the basic ssh functionality is working correctly.
The problem you're seeing is most likely related to your server ssh configuration. When the debugger launches on the remote system, it attempts to make a connection back to your local machine running Eclipse. If you have the "SSH Tunneling" option enabled on the resource manager, then this connection will be made over the main ssh connection using an ssh tunnel. For this to work, your server ssh configuration needs to enable the "GatewayPorts" option. See the sshd_config(5) for more information on this option.
If you are not able to change the sshd configuration on the remote target, the only option is to not use tunneling. This requires direct access from the remote target to your local Eclipse client machine (i.e. you from the remote target system, you should be able to use "ping <local_client_host>".) Also, you'll need to disable the firewall on the local client machine so that the incoming connection is permitted.
Regards,
Greg
On Nov 5, 2010, at 5:04 PM, Chris Genly wrote:
I'm not sure what you mean by a generic remote resource manager.
If I try to launch a simple C program with the existing resource manager nothing appears in the console. A dialog appears and hangs at partial progress. The dialog says:
Progress information
Operation in progress
Upload file.
An exception appears in the error log when I cancel the dialog.
org.eclipse.core.runtime.CoreException: Cannot connect to debugger
at org.eclipse.ptp.debug.internal.core.PSession.connectToDebugger(PSession.java:132)
at org.eclipse.ptp.launch.ParallelLaunchConfigurationDelegate$1$1.run(ParallelLaunchConfigurationDelegate.java:216)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
Chris,
Can you try creating a generic remote launch resource manger, the try debugging a simple non-MPI program using that? I'd like to verify that this works first.
Thanks,
Greg
ptp-user mailing list
ptp-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-user
