It sounds like you have some kind of memory error in your application; you
should run your code through a memory-checking debugger, such as valgrind.
On Jul 24, 2013, at 2:44 AM, Zhubq wrote:
>
>>
>> Hi all,
>>
>> I got a problem when call MPI subroutines in a loop. For example, I have
>>
perfect.. that is exactly what I wanted to know.. that is was an issue with
the program- rather than an issue with openmpi..
Thanks, Jeff.
Matt
_
Matthew MacManes
PhD Candidate
University of California- Berkeley
Museum of Vertebrate Zoology
Phone: 510-495-5833
Lab W
Debugging this is probably not going to be within the scope of Open MPI -- it
looks like your app is seg faulting inside some routine called DoCharset. If
you're getting corefiles, you might try loading them up in the debugger and see
what is going wrong, etc. I.e., standard debugging rules ap
I "unlimited" my stack space- got a different error, which maybe is a clue..
Im not sure how to vary the rank, like you suggested, so if you have a tip
that would be great.
Here is the new error:
[macmanes:05298] *** Process received signal ***
[macmanes:05298] Signal: Segmentation fault (11)
[mac
On Thursday 11 March 2010, Matthew MacManes wrote:
> Can anybody tell me if this is an error associated with openmpi, versus an
> issue with the program I am running (MRBAYES,
> https://sourceforge.net/projects/mrbayes/)
>
> We are trying to run a large simulated dataset using 1,000,000 bases
> div
Can anybody tell me if this is an error associated with openmpi, versus an
issue with the program I am running (MRBAYES,
https://sourceforge.net/projects/mrbayes/)
We are trying to run a large simulated dataset using 1,000,000 bases divided
up into 1000 genes, 5 taxa.. An error is occurring, but w
It's not the valgrind that are telling here -- it's the fact that
something is saying "INJECTING SIGNAL..."
It looks like something in your program is calling abort() (signal 6
is the abort signal).
On Dec 21, 2008, at 4:08 AM, Asad Ali wrote:
--===1267833741==
Content-Type:
Hi Jeff,
I have changed the position of malloc.h in header files list. I moved it up
above mpi.h. Now I am getting a different error message see following,
[asad@stat74 T]$ mpirun --np 4 nice -10 ./lisa09EMRIT-P
+---[ lisa14.c ]---
| This is proc
It looks like your code is failing in malloc, which usually means you
have some kind of memory error.
You might want to try running your code through valgrind, or some
other memory-checking tool...?
On Dec 19, 2008, at 3:34 PM, Asad Ali wrote:
Hi Everybody,
I am running a code in parall
Hi Everybody,
I am running a code in parallel fashion using Open MPI. The code
compiles successfully but when I
run the output executable file I get the following error.
Signal:11 info.si_errno:0(Success) si_code:1(SEGV_MAPERR)
Failing at addr:0xc491f018
[0] func:/usr/lib/openmpi/libopal.so.0 [0x
10 matches
Mail list logo