oug Reeder,
Daniel is saying that the problem only occurs in openmpi when
running more than 16 processes. So could that still be cause
becasue openmpi does not support threads??!!
--- On Fri, 10/3/08, Doug Reeder wrote:
From: Doug Reeder
Subject: Re: [OMPI users] segfault issue - possible bug
cause
becasue openmpi does not support threads??!!
--- On Fri, 10/3/08, Doug Reeder wrote:
From: Doug Reeder
Subject: Re: [OMPI users] segfault issue - possible bug in openmpi
To: "Open MPI Users"
Date: Friday, October 3, 2008, 2:40 PM
Daniel,
Are you using threads. I don't t
Doug Reeder,
Daniel is saying that the problem only occurs in openmpi when running more than
16 processes. So could that still be cause becasue openmpi does not support
threads??!!
--- On Fri, 10/3/08, Doug Reeder wrote:
From: Doug Reeder
Subject: Re: [OMPI users] segfault issue - possible
Daniel,
Are you using threads. I don't think the opempi-1.2.x work with threads.
Doug Reeder
On Oct 3, 2008, at 2:30 PM, Daniel Hansen wrote:
Oh, by the way, here is the segfault:
[m4b-1-8:11481] *** Process received signal ***
[m4b-1-8:11481] Signal: Segmentation fault (11)
[m4b-1-8:11481] S
Oh, by the way, here is the segfault:
[m4b-1-8:11481] *** Process received signal ***
[m4b-1-8:11481] Signal: Segmentation fault (11)
[m4b-1-8:11481] Signal code: Address not mapped (1)
[m4b-1-8:11481] Failing at address: 0x2b91c69eed
[m4b-1-8:11483] [ 0] /lib64/libpthread.so.0 [0x33e8c0de70]
[m4b
I have been testing some code against openmpi lately that always causes it
to crash during certain mpi function calls. The code does not seem to be
the problem, as it runs just fine against mpich. I have tested it against
openmpi 1.2.5, 1.2.6, and 1.2.7 and they all exhibit the same problem.
Also
