[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-user] PTP 1.1 I200701282100 build available
|
I must have done the new->folder instead of the source folder as you indicated.
I did try making a new project and copying my source tree under it and rebulding. However, this did not improve the situation - same results.
Then I tried creating a managed make project and copying all of the source files into that one dir and modifying them so no includes or source is found from other directories. It builds ok. For some reason when I attempt to start the debug it still wants to do a "make -k all". The make is what ever was created by the managed project - but there is no "all" target and it fails.
Even with - or in spite of - the C-Build failure - the debug session still doesn't run. However, I eventually do get a timeout popup on the start of the debugger. The console end says:
accept thread exiting...
event thread starting...
OMPIProxyRuntimeClient got event: EVENT_RUNTIME_PROCATTR job=1 {0}:<> [0]:<ATTRIB_PROCESS_NODE_NAME=ridge05>
*********** 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=ridge05>
*********** 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=ridge05>
*********** 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=ridge05>
*********** 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)
<00000003 QUI>
----- debugger error: Time out - Command Start debugger on Tasks: 0-3 ------------
***** Debugger event: org.eclipse.ptp.debug.external.core.cdi.event.ErrorEvent@2699146a
I do see a two process instances which look like they could be the debugger processes (though I would have expected 4 I think):
krisd 13232 99.9 0.0 71076 7208 ? RL 13:29 12:12 /home/krisd/local/eclipse/plugins/org.eclipse.ptp.linux.x86_64/bin/sdm --host=localhost --debugger=gdb-mi --port=39821 --jobid=2
krisd 13234 0.0
0.0 71116 7284 ? SL 13:29 0:00 /home/krisd/local/eclipse/plugins/org.eclipse.ptp.linux.x86_64/bin/sdm --host=localhost --debugger=gdb-mi --port=39821 --jobid=2
Thanks,
Kris
On 1/30/07, Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
Hi Kris,
On my version of Eclipse, I can only use "new->source folder" to create a folder under the project. I can use "new->folder" to link to a folder outside the project.
Assuming the latter, I think that this is a use case we've not encountered before. We'll take a look and see how to get it to work for you. You definitely don't need a separate project for each binary.
Regarding CVS. You can always create a project in your workspace, then check out the source into the project (Check Out As...) from the CVS Repository Exploring perspective. You'll definitely want to do this to see changes to files under CVS control and use the CVS tools integrated into Eclipse. The Eclipse project files are only stored at the top level, so they should not pollute your source code. A side benefit is that since the source will actually reside under the project, debugging should work without a problem.
Cheers,
Greg
On Jan 30, 2007, at 10:48 AM, Kris Davis wrote:
Well - not quite. The binary and the source are in the same directory and built via a standard make file - not the managed make. However, the project workspace and the source (including binary) are in separate trees. I created the project separate so the project dirs wouldn't end up in my cvs space - then I did an "new->source folder" under the project. This method builds and debugs ok via the CDT plugins, but the debug in PTP doesn't work.
I assume (hope) you mean that it needs to be built "at" the workspace to mean that the source folders need to be a subdir of the workspace folder - I'll give that a try. If you mean that I have to have a separate project for each binary, I'm afraid that might end up to be a problem. I'd like to avoid any eclipse stuff in my cvs source tree (though I'm rather new at using CVS and eclipse - and I'm unsure of the implications).
Regards,
Kris
On 1/30/07, Clement Chu <
clement.chu@xxxxxxxxxxxxxxxxxxxxxx> wrote: Hi Kris,
If I am right, you need to build your program at eclipse's
workspace. Create a new c project and add your source file into it.
(Maybe you need to set mpicc compiler in project properties. See
attachment). Hope this information is useful.
Cheers,
Clement
Clement Chu wrote:
> Hi Kris,
>
> I found what the problem is. In you case, I think you imported the
> binary file into eclipse's workspace (Right?). If you launched to run
> this binary file, it is working fine. But it will cause an error you
> got if you launched this binary file at debug mode. Currently, ptp
> cannot support to debug a program without source file. In coming
> build, I will catch this error to prevent eclipse from freezing.
>
> 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
>
> _______________________________________________
> 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 mailing list
ptp-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-user
