(gdb) bt #0 0x000000360462e21d in raise () from /lib64/tls/libc.so.6 #1 0x000000360462fa1e in abort () from /lib64/tls/libc.so.6 #2 0x0000000002256329 in Petsc_MPI_Abort () #3 0x00000000023fa16b in PetscOptionsInsert () #4 0x00000000023fbe45 in PetscOptionsFindPair_Private () #5 0x00000000023fd5af in PetscOptionsGetString () #6 0x0000000002339d26 in MatMFFDInitializePackage () #7 0x00000000022a2660 in MatInitializePackage () #8 0x0000000002343c4e in MatCreate () 1, does petsc support multiple threads, if I compiled libpetsc.a with -with-mpi=0? 2, is the following usage right? While(1) { ReceiveJobfromServer(); PetscInitialize(); //to avoid a SIGTERM error, I move the call of PetscInitialize into the loop. handleJob(); PetscFinalize(); } Thanks, Debao ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Aron Ahmadia Sent: Tuesday, August 09, 2011 4:39 PM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: PetscFinalize() line 968 in src/sys/objects/pinit.c Debao, What is the complete traceback for this problem? A On Tue, Aug 9, 2011 at 11:12 AM, Debao Shao <[email protected]<mailto:[email protected]>> wrote: DA, Do you happen to know what may cause this error? "[0]PETSC ERROR: PetscFinalize() line 968 in src/sys/objects/pinit.c" After reporting this error, the job can run continued, but it will aborted when encountering next petsc related features even with calling PetscInitialize() again, and say: "Options have not been enabled. You might have forgotten to call PetscInitialize()." Here is line 968: ierr = MPI_Finalize();CHKERRQ(ierr); Thanks, Debao ________________________________ -- 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. ________________________________ -- 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.

I see. Aron, thanks a lot. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Aron Ahmadia Sent: Tuesday, August 09, 2011 5:11 PM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: PetscFinalize() line 968 in src/sys/objects/pinit.c Hi Debao, 1. see http://www.mcs.anl.gov/petsc/petsc-as/miscellaneous/petscthreads.html 2. There is no support for running PetscInitialize after PetscFinalize has been called. Generally these functions are only called in main just after the program has been started and right before it exits. You need to move PetscInitialize to before the loop and PetscFinalize to after the loop. A On Tue, Aug 9, 2011 at 11:58 AM, Debao Shao <[email protected]<mailto:[email protected]>> wrote: (gdb) bt #0 0x000000360462e21d in raise () from /lib64/tls/libc.so.6 #1 0x000000360462fa1e in abort () from /lib64/tls/libc.so.6 #2 0x0000000002256329 in Petsc_MPI_Abort () #3 0x00000000023fa16b in PetscOptionsInsert () #4 0x00000000023fbe45 in PetscOptionsFindPair_Private () #5 0x00000000023fd5af in PetscOptionsGetString () #6 0x0000000002339d26 in MatMFFDInitializePackage () #7 0x00000000022a2660 in MatInitializePackage () #8 0x0000000002343c4e in MatCreate () 1, does petsc support multiple threads, if I compiled libpetsc.a with -with-mpi=0? 2, is the following usage right? While(1) { ReceiveJobfromServer(); PetscInitialize(); //to avoid a SIGTERM error, I move the call of PetscInitialize into the loop. handleJob(); PetscFinalize(); } Thanks, Debao ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Aron Ahmadia Sent: Tuesday, August 09, 2011 4:39 PM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: PetscFinalize() line 968 in src/sys/objects/pinit.c Debao, What is the complete traceback for this problem? A On Tue, Aug 9, 2011 at 11:12 AM, Debao Shao <[email protected]<mailto:[email protected]>> wrote: DA, Do you happen to know what may cause this error? "[0]PETSC ERROR: PetscFinalize() line 968 in src/sys/objects/pinit.c" After reporting this error, the job can run continued, but it will aborted when encountering next petsc related features even with calling PetscInitialize() again, and say: "Options have not been enabled. You might have forgotten to call PetscInitialize()." Here is line 968: ierr = MPI_Finalize();CHKERRQ(ierr); Thanks, Debao ________________________________ -- 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. ________________________________ -- 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. ________________________________ -- 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.