Re: [ptp-user] System error: Broken pipe when running under debug

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [ptp-user] System error: Broken pipe when running under debug

From: "mark hauschild" <omgmark@xxxxxxxxxxx>
Date: Wed, 25 Jul 2007 14:51:01 +0000
Delivered-to: ptp-user@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/listinfo/ptp-user>
List-help: <mailto:ptp-user-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/ptp-user>, <mailto:ptp-user-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/ptp-user>, <mailto:ptp-user-request@eclipse.org?subject=unsubscribe>

Okay, I reran the debug with SDM set with --debug=8. Below is the outputfrom it. Quite a bit of information, I hope it makes more sense to you thanme.

We are really looking forward to debugging with eclipse, so I will go to anylengths to get this to work. Just let me know what i need to do!


Mark Hauschild
University of Missouri-St. Louis

XXXXXXXXXXX refreshRuntimeSystems(false), isInitialized():true
sessionCreate(0,0)
bind(0.0.0.0/0.0.0.0:0)
port=48418
XXXXXXXXXXXX   Waiting for Universe to Populate
MODEL MANAGER: newJob(2)
accept thread starting...
ModelManager.run() - new JobID = 2
JAVA OMPI: run() with args:
name:           Sieve
path:           /state/partition1/home/mwh308/workspace/Sieve/Debug
cwd:            /state/partition1/home/mwh308/workspace/Sieve
machineName:    Machine0
#procs:         6
#proc/node:     1
firstNode#:     0
isDebug?                true

<00000354 RUN 6:6a6f62494400 2:3200 9:657865634e616d6500 6:536965766500b:70617468546f457865630034:2f73746174652f706172746974696f6e312f686f6d652f6d77683330382f776f726b73706163652f53696576652f446562756700b:6e756d4f6650726f637300 2:3600 d:70726f63735065724e6f646500 2:3100d:66697273744e6f64654e756d00 2:3000 b:776f726b696e67446972002e:2f73746174652f706172746974696f6e312f686f6d652f6d77683330382f776f726b73706163652f5369657665008:70726f6741726700 6:353030303000 d:6465627567676572506174680040:2f7573722f6c6f63616c2f65636c697073652f706c7567696e732f6f72672e65636c697073652e7074702e6c696e75782e7838365f36342f62696e2f73646d00c:646562756767657241726700 11:2d2d686f73743d6c6f63616c686f737400c:646562756767657241726700 12:2d2d64656275676765723d6764622d6d6900c:646562756767657241726700 a:2d2d64656275673d3800 c:646562756767657241726700d:2d2d706f72743d343834313800>++++++++++ ptp_orte_proxy: (debug ? 1) Spawning 6 processes of job'/state/partition1/home/mwh308/workspace/Sieve/Debug/Sieve'++++++++++ ptp_orte_proxy: program name'/state/partition1/home/mwh308/workspace/Sieve/Debug/Sieve'

++++++++++ ptp_orte_proxy: SPAWNED [error code 0 = 'Success'], now unlocking
++++++++++ ptp_orte_proxy: NEW JOBID = 4
++++++++++ ptp_orte_proxy: registering IO forwarding - name = ''
++++++++++ ptp_orte_proxy: Returning from ORTERun
OMPIProxyRuntimeClient got event: EVENT_RUNTIME_JOBSTATE (jobid=2) state=1
*********** JOB STATE CHANGE: starting (job = job2)

OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=2 {0}:<>[0]:<ATTRIB_PROCESS_NODE_NAME=voyager.umsl.edu>

*********** PROC ATTRIBUTE CHANGE: (job = job2)
setting node[job2_process0]=voyager.umsl.edu(0)

OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=2 {0}:<>[1]:<ATTRIB_PROCESS_NODE_NAME=voyager.umsl.edu>

*********** PROC ATTRIBUTE CHANGE: (job = job2)
setting node[job2_process1]=voyager.umsl.edu(0)

OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=2 {0}:<>[2]:<ATTRIB_PROCESS_NODE_NAME=voyager.umsl.edu>

*********** PROC ATTRIBUTE CHANGE: (job = job2)
setting node[job2_process2]=voyager.umsl.edu(0)

OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=2 {0}:<>[3]:<ATTRIB_PROCESS_NODE_NAME=voyager.umsl.edu>

*********** PROC ATTRIBUTE CHANGE: (job = job2)
setting node[job2_process3]=voyager.umsl.edu(0)

OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=2 {0}:<>[4]:<ATTRIB_PROCESS_NODE_NAME=voyager.umsl.edu>

*********** PROC ATTRIBUTE CHANGE: (job = job2)
setting node[job2_process4]=voyager.umsl.edu(0)

OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=2 {0}:<>[5]:<ATTRIB_PROCESS_NODE_NAME=voyager.umsl.edu>

*********** PROC ATTRIBUTE CHANGE: (job = job2)
setting node[job2_process5]=voyager.umsl.edu(0)
OMPIProxyRuntimeClient got event: EVENT_RUNTIME_JOBSTATE (jobid=2) state=2
*********** JOB STATE CHANGE: running (job = job2)
accept thread exiting...
event thread starting...
*** SEND COMMAND: Start debugger, tasks: 0-5

<000000ed INI 6:53696576650034:2f73746174652f706172746974696f6e312f686f6d652f6d77683330382f776f726b73706163652f53696576652f4465627567002e:2f73746174652f706172746974696f6e312f686f6d652f6d77683330382f776f726b73706163652f5369657665006:353030303000>++++++++++ ptp_orte_proxy: MI: SEND -gdb-set environmentOMPI_MCA_ns_nds_jobid=4++++++++++ ptp_orte_proxy: SDM[8,1]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: MI: SEND -gdb-set environmentOMPI_MCA_ns_nds_jobid=4++++++++++ ptp_orte_proxy: MI: SEND -gdb-set environmentOMPI_MCA_ns_nds_jobid=4++++++++++ ptp_orte_proxy: SDM[8,3]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,0]: ------------------- SendCommandWaitsess->out_fd = -1

got debug event: EVENT_DBG_OK 3f
*** SET COMMAND RETURN: Start debugger, result: OK, tasks: 0-5

++++++++++ ptp_orte_proxy: MI: SEND -gdb-set environmentOMPI_MCA_ns_nds_jobid=4++++++++++ ptp_orte_proxy: SDM[8,2]: ------------------- SendCommandWaitsess->out_fd = -1

*** SEND COMMAND: Set line breakpoint, tasks: 0-5

<00000054 SLB 5:363a336600 2:3000 2:3000 2:3000 8:73696576652e6300 3:3633001:00 2:3000 2:3000>++++++++++ ptp_orte_proxy: MI: SEND -gdb-set environmentOMPI_MCA_ns_nds_jobid=4++++++++++ ptp_orte_proxy: SDM[8,5]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: MI: SEND -gdb-set environmentOMPI_MCA_ns_nds_jobid=4++++++++++ ptp_orte_proxy: SDM[8,1]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,4]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,0]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,2]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,3]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,5]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,1]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,0]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,2]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,3]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,4]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,5]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,1]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,0]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,2]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,3]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,4]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,5]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,1]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,0]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,2]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,3]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,4]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,5]: ------------------- SendCommandWaitsess->out_fd = -1got debug event: EVENT_DBG_ERROR 3f 12 No source file named "System error:Broken pipe"*** SET COMMAND RETURN: Set line breakpoint, result:org.eclipse.ptp.debug.core.cdi.PCDIException: No source file named "Systemerror: Broken pipe"[], tasks: 0-5----- debugger error: No source file named "System error: Broken pipe" onTasks: 0-5 ------------***** Debugger event:org.eclipse.ptp.debug.external.core.cdi.event.ErrorEvent@1b92d8d6

<00000003 QUI>
<00000003 QUI>

++++++++++ ptp_orte_proxy: SDM[8,4]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,3]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,1]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,0]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,2]: ------------------- SendCommandWaitsess->out_fd = -1

event thread exiting...

++++++++++ ptp_orte_proxy: SDM[8,4]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,5]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,3]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,1]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,0]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,2]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,4]: ------------------- SendCommandWaitsess->out_fd = -1++++++++++ ptp_orte_proxy: SDM[8,5]: ------------------- SendCommandWaitsess->out_fd = -1

++++++++++ ptp_orte_proxy: shutdown completed
OMPIProxyRuntimeClient got event: EVENT_RUNTIME_JOBSTATE (jobid=2) state=3
*********** JOB STATE CHANGE: exited (job = job2)

Message: 1
Date: Mon, 23 Jul 2007 14:50:30 -0600
From: Greg Watson <g.watson@xxxxxxxxxxxx>
Subject: Re: [ptp-user] System error: Broken pipe when running under
	debug
To: PTP User list <ptp-user@xxxxxxxxxxx>
Message-ID: <7BE6808C-8782-4875-83F4-55B3E556FA8E@xxxxxxxxxxxx>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

Mark,

It looks like the gdb that the debugger uses to control the process
may be crashing when it is trying to insert a breakpoint at main().
Can you go into the SDM preferences (PTP->Debug->SDM) and add the
following to 'Extra SDM arguments':

--debug=8

Then rerun the debug session and send me the output you're getting.

Thanks,

Greg

On Jul 23, 2007, at 9:41 AM, mark hauschild wrote:

> Hello again,
>
> We just recently got in some new 64bit boards and I installed
> eclipse_64 versions of eclipse, cdt and the ptp. Running things is
> working great, but when I try and debug I get an error I am not
> familiar with...
>
> After running under debug with 6 processes, I get the following
> error window popup
> "Error on tasks: 0-5 - No source file named "system error: Broken
> pipe""
>
> followed by the window
> "Exception occurred during launch"
> Reason:
>  No source file named "System error: Broken pipe"
>
> Pasted below is the terminal output. I have a feeling this might be
> a problem on my end, as broken pipe sounds like something messed up
> on our server, but in the off chance that this is a common problem
> with ptp and debug I decided to post here. Any ideas or advice or
> things to look at would be appreciated!
>
> Mark Hauschild
> University of Missouri - St. Louis
>
>
> got debug event: EVENT_DBG_OK 3f
> *** SET COMMAND RETURN: Start debugger, result: OK, tasks: 0-5
> *** SEND COMMAND: Set line breakpoint, tasks: 0-5
> <00000060 SLB 5:363a336600 2:3000 2:3000 2:3000 e:
> 68656c6c6f5f776f726c642e6300 3:323600 1:00 2:3000 2:3000>
> got debug event: EVENT_DBG_ERROR 3f 12 No source file named "System
> error: Broken pipe"
> *** SET COMMAND RETURN: Set line breakpoint, result:
> org.eclipse.ptp.debug.core.cdi.PCDIException: No source file named
> "System error: Broken pipe"[], tasks: 0-5
> ----- debugger error: No source file named "System error: Broken
> pipe" on Tasks: 0-5 ------------
> ***** Debugger event:
> org.eclipse.ptp.debug.external.core.cdi.event.ErrorEvent@4b19b8ae
> <00000003 QUI>
> <00000003 QUI>
> event thread exiting...
> ++++++++++ ptp_orte_proxy: shutdown completed
> OMPIProxyRuntimeClient got event: EVENT_RUNTIME_JOBSTATE (jobid=11)
> state=3
> *********** JOB STATE CHANGE: exited (job = job11)
>
> _________________________________________________________________
> Local listings, incredible imagery, and driving directions - all in
> one place! http://maps.live.com/?wip=69&FORM=MGAC01
>
> _______________________________________________
> 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


End of ptp-user Digest, Vol 8, Issue 11
***************************************


_________________________________________________________________
http://newlivehotmail.com

Prev by Date: Re: [ptp-user] System error: Broken pipe when running under debug
Next by Date: [ptp-user] Re: System error: Broken pipe when running under debug
Previous by thread: Re: [ptp-user] System error: Broken pipe when running under debug
Next by thread: [ptp-user] Re: System error: Broken pipe when running under debug
Index(es):
- Date
- Thread

Breadcrumbs