| Re: [ptp-dev] M5 build candidate |
| First, check that the resource manager you created is set for version 1.2. Next, when you start eclipse with the -debug argument (from the command line), it should display a bunch of stuff, then something about a Debug options file. If you create/edit this file and add one or more of the following lines, you should be able to get more debugging output. Let me know what you find out. Greg # Tracing org.eclipse.ptp.rm.core/debug=true # Trace jobs that execute remote commands (discover, monitor, etc) org.eclipse.ptp.rm.core/debug/command=true # Trace more details about jobs that execute remote commands (discover, monitor, etc) org.eclipse.ptp.rm.core/debug/command/more=true # Trace job submission on the Runtime System org.eclipse.ptp.rm.core/debug/job=falsetrue # Trace status of the Runtime System org.eclipse.ptp.rm.core/debug/rts=true # Trace discover procedure on the Runtime System org.eclipse.ptp.rm.core/debug/rts/discover=true # Trace monitor procedure on the Runtime System org.eclipse.ptp.rm.core/debug/rts/monitor=true # Trace status of IPJobs on the Runtime System org.eclipse.ptp.rm.core/debug/rts/job=true # Trace more details of IPJobs on the Runtime System org.eclipse.ptp.rm.core/debug/rts/job/more=true # Redirect output of parallel application to terminal that is running eclipse org.eclipse.ptp.rm.core/debug/rts/job/output=true On Oct 7, 2008, at 3:45 PM, Wyatt Spear wrote:
|