I think there is something wrong in the way the application is built,
or in the way you run collect. We run MPI tests every night, so at
least simple tests should work just fine. Could you, please, send me
more details about your MPI and your application?

1. MPI version strings

which mpicc

mpicc -version

which mpirun

mpirun -version

2. Analyzer version strings

collect -V

analyzer -V

3. Experiment listing

ls -lR test.1.er

4. Log file (starting from the collect command):

collect -M OPENMPI mpirun -np 2 -- hello

...

analyzer test.1.er

...

5. The application itself (source code or binary).

I'll run this application on our system, and let you know
the result.

Thanks,
Nik

Leo P. wrote:

HI Nik,

I tried the Sun Studio Performance Analyzer and it was able to profile
to application but not the openMPI source code. The source code was
empty in Sun Studio Performance Analyzer. I tried but i was not able to
get the profiling information of openMPI.

So i installed Vampir trace and i was able to get otf while suggested i
got the profiling information. But i fail to understand what i should
do now. 1. Am i suppose to download additional information for trace
information visualization? Is the additional software this https://www.ssl-id.net/www.vampir.eu/index.html
2. If not how can i visualize the trace information i got vampir-trace.

Sorry for bugging everyone so much about this. But i spend a lot of
time and this alone and i am not getting output.

Final version will be available soon, but EA should be good enough
to try :-) I suggest you to download EA as a tar file, extract it,
set PATH, and run the following commands:

$ collect -M OPENMPI mpirun -np 2 -- hello

Note: it is necessary to add "--" after mpirun arguments.
This command will create a "test.1.er" directory (experiment).
To view the experiment, run "analyzer" (Java GUI tool):

$ analyzer test.1.er

If everything works properly you will see MPI Timeline and other tabs,
that show profiling information. Please, make sure you have java 1.5 or
newer in your PATH.

Thanks,
Nik

Leo P. wrote:

Also i was wondering
whether gdb could be used with openMPI. I know
about -d option in mpirun but i need to use gdb if its possible. I
think i have done all the necessary things to enable profiling and
debuging but i am missing something here.

Sorry guys i forgot i could debug shared library function in gdb. :) So
currently using

$ mpirun -np 1 xterm -e gdb hello

to debug the openMPI source.

If only i could get the profiling information, it could help me a lot.

Also i was wondering whether gdb could be used with openMPI. I know
about -d option in mpirun but i need to use gdb if its possible. I
think i have done all the necessary things to enable profiling and
debuging but i am missing something here.