Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ptp-dev] PTP 7.0.4 bug? MPICH, debugger, openmpi monitor

On Feb 25, 2014, at 11:03 AM, Beth Tibbitts <beth@xxxxxxxxxx> wrote:



Dave it sounds like these warrant bugzillas?  Or at least more discussion. Not sure everyone read through your test report..   

1. mpich2 launch error popup, resources tab blank

This sounds like a bug.

2. your 8) are there printlns in sdm or our debugger? doesn't bother me, perhaps useful.

Yes, they have been there forever. 

3. your 9) should you have to create a monitor? shouldn't it be created automagically?   Or at least should you be able to explicitly create one?

The MPICH2, OpenMPI and PE target configurations no longer have monitors defined. Output is displayed directly in the console. The monitor component still supports them, so you can define them manually if you want, but they are not needed for interactive runs.

...Beth

Beth Tibbitts


On Fri, Feb 21, 2014 at 6:58 PM, David Wootton <drwootton@xxxxxxxxxx> wrote:
I ran some tests on Linux x86_64.

Most importantly, I created a run configuration for shallow as a MPICH2 application. When I clicked the resources tab in the run configuration, selected the MPICH2 target system configuration and my machine as the host I got an error popup "Failed to create control for the dynamic tab "Basic Options" Reason: Undefined attribute "noLocalOption" in widget type

Then the resources tab was blank except for the target system configuration name and connection name. There were no MPICH settings.

I rebuilt shallow as an OpenMPI project and it ran fine, no errors.

Beyond that:
1) Created a synchronized project for shallow
2) Set up include directory for MPI headers and ran code analysis. All the red markers in the source files were gone
3) Checked a few symbol references and symbol definitions. The few I spot-checked were correct
4) Ran MPI artifacts, looked correct
5) Ran MPI barrier analysis which found an error at line 88 of main.c. This might be the buggy version of shallow I'm using. Not sure exactly which version I have.
6) Ran project clean and then built shallow. No problems.
7) Created a run configuration for shallow and ran it. No problems.
8) Invoked the debugger on shallow and single stepped a few instructions. Seemed ok except the xterm where I invoked Eclipse displays some debug messages, I think from AbstractEventManager,  EventRequestManager, NotifyJob and maybe a few others
9) I never saw any OpenMPI job show up in the active or inactive jobs view. I think this is because I didn't have a monitor for OpenMPI (There isn't one in the dropdown to add new monitors so it probably doesn't exist)

Dave

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


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

Back to the top