Thanks a lot, Jed and Aron.

 

Do you have ideas for this problem?

 

But I encounter a new problem, the situation is:

1, the matrix is big, and can be partitioned to several blocks;

2, started several threads to handle each block of matrix;

3, integrated all block matrices together.

 

Again, the program crashed with reporting:

"[0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range"

 

My libpetsc.a is built with option "--with-mpi=0 --with-debugging=0 -with-log=0 -with-info=0".

Will it support this type of multiple threads?

 

Thanks,

Debao

From: petsc-users-bounces@mcs.anl.gov [mailto:petsc-users-bounces@mcs.anl.gov] On Behalf Of Jed Brown
Sent: Friday, August 05, 2011 9:26 PM
To: PETSc users list
Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate

 

On Fri, Aug 5, 2011 at 04:00, Debao Shao <Debao.Shao@brion.com> wrote:

1, I put "PetscInitialize" at the beginning of main, and "PetscInitialize" registers a signal handler to capture "SIGTERM";

2, the problem ran in server side will send SIGTERM to kill all of clients after one stage is done.

3, then, unfortunately, the signal "SIGTERM" is caught by the signal handler installed by "PetscInitialize", and caused to abort.

You can remove the order dependence by running with -no_signal_handler or setting your own signal handler with:

 

http://www.mcs.anl.gov/petsc/petsc-as/snapshots/petsc-dev/docs/manualpages/Sys/PetscPushSignalHandler.html


-- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities. To the extent you are relying on this information, you are doing so at your own risk. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ASML is neither liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt.