FWIW, the stack trace is telling you that it segv'ed in a printf in the main()
function of your application. If it dumped core, you can just attach to the
core file and see exactly where it died.
On Jul 25, 2010, at 10:08 PM, Jack Bryan wrote:
> Dear All,
>
> I run a 6 parallel processes on
What do you mean short and long? Do you have the ability to control
the execution time of your program without changing a single line of
your code?
On 7/25/10, Jack Bryan wrote:
>
> Dear All,
> I run a 6 parallel processes on OpenMPI.
> When the run-time of the program is short, it works well.
>
>
>> Date: Mon, 26 Jul 2010 08:23:57 +0200
>> From: jody....@gmail.com
>> To: us...@open-mpi.org
>> Subject: Re: [OMPI users] OpenMPI Segmentation fault (11)
>>
>> Hi Jack
>>
>> Have you tried to run your aplication under valgrind?
>> Even thoug
Thanks
It can be installed on linux and work with gcc ?
If I have many processes, such as 30, I have to open 30 terminal windows ?
thanks
Jack
> Date: Mon, 26 Jul 2010 08:23:57 +0200
> From: jody@gmail.com
> To: us...@open-mpi.org
> Subject: Re: [OMPI users] OpenMPI Segmentati
Hi Jack
Have you tried to run your aplication under valgrind?
Even though applications generallay run slower under valgrind,
it may detect memory errors before the actual crash happens.
The best would be to start a terminal window for each of your processes
so you can see valgrind's output for ea
Dear All,
I run a 6 parallel processes on OpenMPI.
When the run-time of the program is short, it works well.
But, if the run-time is long, I got errors:
[n124:45521] *** Process received signal ***[n124:45521] Signal: Segmentation
fault (11)[n124:45521] Signal code: Address not mapped (1)[n124:
