Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ptp-user] Remote parallel debugger won't initialize.
Joshua,
Can you confirm that
(a) you're using a run configuration, parallel application,  with the 'remote' machine and it runs ok (you will need a 'connection' to the cluster), then 
(b) a 'debug' configuration should be the same with the debugger tab is all that is new.
It *should* copy the sdm for the appropriate target (e.g. Linux), you shouldn't have to build it.
Do you have checked "Use built-in SDM if available for the target platform" on the Debugger tab??  Or did you build the sdm? where did you put it?

(c) I assume you are building your app locally (on local machine, on shared file system with cluster) then the 'remote' execution in your run configuration for the Parallel Application refers to the executable, on the Application tab, with respect to that cluster machine right?


...Beth

Beth Tibbitts


On Thu, Oct 3, 2013 at 12:05 PM, Joshua Strodtbeck <joshua.strodtbeck@xxxxxxxxxxxxxxx> wrote:
Beth,

I'm using PTP 7.0.3.201308141.

I just manually copied SDM to the appropriate folder. Upon further investigation, it appears that sdm will run if I execute it on my local machine, but not on the remote destination machine (I typed './sdm' at the terminal to just see what would happen), where it delivers a floating point exception. Both are x86 machines running Linux. Should I build a different SDM executable to run on the remote machine?

-JPS

One of our IT guys built and installed this, so I may not beable
On 10/03/2013 10:52 AM, Beth Tibbitts wrote:
Joshua, 
Can you tell us exactly what version of PTP is installed?

I presume for running, you're setting up the PTP run configuration to connect to the remote system (on the Resources tab) - so to debug using a similar debug configuration, I believe that the path to sdm (set on the Debugger tab of the debug configuration) should be valid from the 'remote' system you're connecting to (not relative to your local machine, you said there is a shared file system)

Did you build/move sdm there yourself, or are you relying on PTP 7.0.x ability to automatically move it there during debug launch, or what?
Just want to clarify since your situation has the shared file system.  

...Beth

Beth Tibbitts


On Thu, Oct 3, 2013 at 11:43 AM, Joshua Strodtbeck <joshua.strodtbeck@xxxxxxxxxxxxxxx> wrote:
I've got an issue with starting up the debugger (using Kepler, Linux, x86) that doesn't seem to correspond to anyone else's problem. I'm working on a system where the cluster and the workstation share a file system, so I do all my editing locally, then run using a remote session. It runs fine (though it won't output to the console until I kill the job for some reason).

Now wen I set up the debugger, I use the same parallel settings. I've got the SDM executable sitting in one of my PATH directories. However, when I try to execute a debug session, it dies immediately, and I get this:

363a2069-bf31-46f5-88d9-40f907256d3c: FAILED
#PTP job_id=21990

--------------------------------------------------------------------------
mpirun noticed that process rank 0 with PID 21994 on node quad40 exited on signal 8 (Floating point exception).
--------------------------------------------------------------------------

Not sure why I'd be getting a floating point exception. Anyone run into a similar issue and can help?

--

Joshua Strodtbeck, PhD | Research Engineer

Convergent Science

O: (608) 831-3811

Never make a mesh again!

_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-user




_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-user


_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-user


Back to the top