[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ptp-user] PTP 1.1 I200701282100 build available
|
I have openmpi in the library path. Is there something I need to explicitly add for PTP?
On 1/30/07, Clement Chu <
clement.chu@xxxxxxxxxxxxxxxxxxxxxx> wrote:Hi Kris,
Did you set LD_LIBRARY_PATH?
Regards,
Clement
Kris Davis wrote:
> OS= Red Hat Enterprise Linux AS (2.6.9-34.ELsmp)
>
> gdb --version
> GNU gdb Red Hat Linux (6.3.0.0-1.96rh)
> This GDB was configured as "x86_64-redhat-linux-gnu".
>
> The app does run ok without debugging - I'm able to do the "run..."
> operation, see and query the process info ok in the PTP Run perspective.
>
> Running the GDB debugger via mpirun seems to work fine:
> i.e.: mpirun --prefix /home/krisd/local/openmpi -np 4 -d xterm -e
> /usr/bin/gdb bandwidth.rts
>
>
> Upon starting a parallel debug session within eclipse - it decided it
> needed to rebuild I think - the C-build console says:
> make -k
> make: *** No targets specified and no makefile found. Stop"
> I'm not sure why it thinks it needs to rebuild the image as it is up
> to date otherwise. Maybe that's a clue.
>
> But - eclipse is hung - can't click - mouse Icon is mostly the
> "clock". The start up was set to break on "main".
>
> The eclipse console up to the hang is attached as
eclipse.console.log.
>
>
> I tried again - looking for a reason why it would want to rebuild.
> Didn't see anything - but changed the current working directory in the
> debug panels from "default" to a "local dir" and explicitly changed to
> the dir where the binary resided. This time I received an error
> popup I've attached as "Fatal PTP err.jpg". The console log is
> attached as eclipse-2.console.log (includes a ctl-C to terminate
> eclipse).
>
>
> I made a 3rd attempt after having run the "cleanupOmpi.sh". But, I
> still get the fatal PTP error popup.
>
>
> On the 4th attempt - I changed the "arguments" setting for the current
> working directory back to the "default" and it returns to the eclipse
> hang - no error popup. It still seems to want to rebuild though.
>
> Thanks much
>
> Kris
>
> On 1/29/07, *Greg Watson* <g.watson@xxxxxxxxxxxx
> <mailto:g.watson@xxxxxxxxxxxx>> wrote:
>
> Kris,
>
> We stopped shipping binaries in version 1.0, so you won't see them
> any more. You did the correct thing running the BUILD script though.
>
> Can you please let me know your linux version and the version of
> gdb you have installed. Are you able to run the application
> (without debugging) either from Eclipse or the command line? Also,
> if you could try running another debug session and send me all the
> console output it would be appreciated. There's nothing in the one
> you sent about debugging.
>
> Thanks,
>
> Greg
>
> On Jan 29, 2007, at 1:45 PM, Kris Davis wrote:
>
>> I loaded this new build ok. It was missing the orte binaries for
>> linux.x86_64, so I I just did an "sh BUILD" in that dir and it
>> seemed to work ok.
>>
>> Now I'm able to do the view the parallel run time jobs. However,
>> when I attempt a parallel debug session, the eclipse session
>> hanges with the "Starting the Job..." popup active. The "sdm"
>> process sit's at ~100% of 1 CPU. I don't see any other messages.
>> Is there someplace else to look for messages? The eclipse
>> console session does show processes starting (I just indicated
>> 4) - here is the eclipse console:
>>
>> ++++++++++ ptp_orte_proxy: SPAWNED [error code 0 = 'Success'],
>> now unlocking
>> ++++++++++ ptp_orte_proxy: NEW JOBID = 2
>> ++++++++++ ptp_orte_proxy: registering IO forwarding - name = ''
>> ++++++++++ ptp_orte_proxy: Returning from ORTERun
>> OMPIProxyRuntimeClient got event: EVENT_RUNTIME_JOBSTATE
>> (jobid=1) state=1
>> *********** JOB STATE CHANGE: starting (job = job1)
>> accept thread exiting...
>> <000000dd INI
>> 47:62656e63686d61726b732f706572666f726d616e63652f6d696e692d62656e63686d61726b732f66617474
>>
>> 7265652f62616e6477696474682f62616e6477696474682e72747300
>> 10:2f686f6d652f6b726973642f73726300 10:2f686f6
>> d652f6b726973642f73726300>
>> event thread starting...
>> OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=1
>> {0}:<> [0]:<ATTRIB_PROCESS_NODE_NAME=ri
>> dge05>
>> *********** PROC ATTRIBUTE CHANGE: (job = job1)
>> setting node[job1_process0]=ridge05(0)
>> OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=1
>> {0}:<> [1]:<ATTRIB_PROCESS_NODE_NAME=ri
>> dge05>
>> *********** PROC ATTRIBUTE CHANGE: (job = job1)
>> setting node[job1_process1]=ridge05(0)
>> OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=1
>> {0}:<> [2]:<ATTRIB_PROCESS_NODE_NAME=ri
>> dge05>
>> *********** PROC ATTRIBUTE CHANGE: (job = job1)
>> setting node[job1_process2]=ridge05(0)
>> OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=1
>> {0}:<> [3]:<ATTRIB_PROCESS_NODE_NAME=ri
>> dge05>
>> *********** PROC ATTRIBUTE CHANGE: (job = job1)
>> setting node[job1_process3]=ridge05(0)
>> OMPIProxyRuntimeClient got event: EVENT_RUNTIME_JOBSTATE
>> (jobid=1) state=2
>> *********** JOB STATE CHANGE: running (job = job1)
>>
>>
>> Thanks for your help
>>
>> Kris
>>
>>
>> On 1/29/07, *Greg Watson* < g.watson@xxxxxxxxxxxx
>> <mailto:g.watson@xxxxxxxxxxxx>> wrote:
>>
>> Hi all,
>>
>> I just uploaded the I200701282100 build to the download
>> server. You
>> can get it from
http://www.eclipse.org/ptp/builds.php.
>>
>> Unfortunately the latest version of OpenMPI ( 1.2b3) changed
>> a number
>> of interfaces that break the ORTE proxy. This build attempts to
>> address this issue. I've done some testing on MacOSX and
>> Linux and it
>> appears to work correctly, but the new interfaces are not yet
>> documented, so I may not be using them correctly. I will try
>> and get
>> more information over the next few days.
>>
>> *** NOTE ***
>>
>> This build will ONLY work with OpenMPI 1.2b3 (and later,
>> presumably)
>> or OpenMPI 1.0.2. Older versions of OpenMPI 1.2 (1.2b1, etc.)
>> are no
>> longer supported. Please update your version of OpenMPI if
>> necessary.
>> Downloads are available from http://open-mpi.org/.
>>
>> Greg
>>
>> _______________________________________________
>> ptp-user mailing list
>> ptp-user@xxxxxxxxxxx <mailto:ptp-user@xxxxxxxxxxx>
>>
https://dev.eclipse.org/mailman/listinfo/ptp-user
>>
>>
>> _______________________________________________
>> ptp-user mailing list
>> ptp-user@xxxxxxxxxxx <mailto:ptp-user@xxxxxxxxxxx>
>>
https://dev.eclipse.org/mailman/listinfo/ptp-user
>> <https://dev.eclipse.org/mailman/listinfo/ptp-user>
>
>
> _______________________________________________
> ptp-user mailing list
> ptp-user@xxxxxxxxxxx <mailto: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