Hi
sorry, adding the path of my source code to the search path solved this
problem,
thanks,
Manal
On Fri, 2006-07-14 at 18:01 +1000, Manal Helal wrote:
> Hi
>
> I tried your suggestion:
>
> mpirun --debug -np 4 a.out
>
> and I have TV and openMPI 1.1, and it worked fine, thats on Fedora C5
Hi
I tried your suggestion:
mpirun --debug -np 4 a.out
and I have TV and openMPI 1.1, and it worked fine, thats on Fedora C5
and x86 intel chip, single machine
however, my problem, this starts TV with the mpirun program itself being
debugged, but then starts my program and I see the output up t
...@open-mpi.org
> [mailto:users-boun...@open-mpi.org] On Behalf Of Andrew J Caird
> Sent: Wednesday, July 05, 2006 9:16 PM
> To: Open MPI Users
> Subject: Re: [OMPI users] OpenMPI, debugging, and Portland
> Group's pgdbg
>
>
> This took a long time for me to get to, but once I
This took a long time for me to get to, but once I did, what I found was
that the closest thing to working for the PGI compilers with OpenMPI is
this command:
mpirun --debugger "pgdbg @mpirun@ @mpirun_args@" --debug -np 2 ./cpi
It appears to work, that is, you can select a process with the
ething else.
> -Original Message-
> From: users-boun...@open-mpi.org
> [mailto:users-boun...@open-mpi.org] On Behalf Of Caird, Andrew J
> Sent: Tuesday, June 13, 2006 4:38 PM
> To: us...@open-mpi.org
> Subject: [OMPI users] OpenMPI, debugging, and Portland Group's
Hello all,
I've read the thread "OpenMPI debugging support"
(http://www.open-mpi.org/community/lists/users/2005/11/0370.php) and it
looks like there is improved debugging support for debuggers other than
TV in the 1.1 series.
I'd like to use Portland Groups pgdbg. It's a parallel debugger,
there
