Hi Martin,
Thanks for the information. So it will be changed also for memchecker.
Regards,
Shiqing
The (non modifying) access to a send buffer was agreed for MPI Standard 2.2 not version 2.1 see the MPI 2.2 Wiki:
https://svn.mpi-forum.org/trac/mpi-forum-web/wiki/MpiTwoTwoWikiPage
htt
Ralph Castain wrote:
Hi Ray
Are the jobs that leave files behind terminating normally or aborting?
Are there any warnings/error messages out of mpirun?
Just trying to determine if this is an abnormal termination issue or a
bug in OMPI itself.
Ralph
As far as I know, they are from jobs t
4) Well, this sounds reasonable, but according to the MPI-1 standard
(see page 40 for non-blocking send/recv, a more detailed explanation in
page 30):
"A nonblocking send call indicates that the system may start copying
data out of the send buffer. The sender shoul
Hi George,
4) Well, this sounds reasonable, but according to the MPI-1 standard
(see page 40 for non-blocking send/recv, a more detailed explanation in
page 30):
"A nonblocking send call indicates that the system may start copying
data out of the send buffer. The sender should */not access*/ a
On Nov 19, 2008, at 10:18 , François PELLEGRINI wrote:
4) Well, this sounds reasonable, but according to the MPI-1 standard
(see page 40 for non-blocking send/recv, a more detailed
explanation in
page 30):
"A nonblocking send call indicates that the system may start copying
data out of the
Bonjour Shiqing,
Shiqing Fan wrote:
> Dear François,
>
> Thanks a lot for your report, it's really a great help for us. :-)
No problem. Your software helps me too, so as soon as you have fixes
and new builds please tell me, so that I can try again.
> For the issues:
> 1) When you got "Condit
Hi Ray
Are the jobs that leave files behind terminating normally or aborting?
Are there any warnings/error messages out of mpirun?
Just trying to determine if this is an abnormal termination issue or a
bug in OMPI itself.
Ralph
On Nov 19, 2008, at 8:05 AM, Ray Muno wrote:
Thought I wo
2008/11/19 Ray Muno
> Thought I would revisit this one.
>
> We are still having issues with this. It is not clear to me what is leaving
> the user files behind in /dev/shm.
>
> This is not something users are doing directly, they are just compiling
> their code directly with mpif90 (from OpenMPI)
Thought I would revisit this one.
We are still having issues with this. It is not clear to me what is
leaving the user files behind in /dev/shm.
This is not something users are doing directly, they are just compiling
their code directly with mpif90 (from OpenMPI), using various compilers.
Co
Dear François,
Thanks a lot for your report, it's really a great help for us. :-)
For the issues:
1) When you got "Conditional jump" errors, normally that means some
uninitialized(or undefined) values were used. The parameters that passed
into PMPI_Init_thread might contain uninitialized va
Gabriele Fatigati wrote:
Ok,
but in Ompi 1.3 how can i enable it?
This may not be relevant, but I could not get a hybrid mpi+OpenMP code
to work correctly.
Would my problem be related to Gabriele's and perhaps fixed in openmpi 1.3?
Stephen
2008/11/18 Ralph Castain :
I am afraid it is on
Hello all,
I am the main developer of the Scotch parallel graph partitioning
package, which uses both MPI and Posix Pthreads. I have been doing
a great deal of testing of my program on various platforms and
libraries, searching for potential bugs (there may still be some ;-) ).
The new memchec
12 matches
Mail list logo
