Hello If a mesh is partitioned using Metis but the original order of nodes is used to create/partition the matrix then would this be significantly bad for performance and scalability. Also is there an example that uses Metis to partition an unstructured mesh? Thanks in advance. Tabrez
On Thu, Aug 4, 2011 at 11:31 PM, Tabrez Ali <[email protected]> wrote:
Hello
If a mesh is partitioned using Metis but the original order of nodes is used to create/partition the matrix then would this be significantly bad for performance and scalability.
That depends. Many mesh generators h ave fairly good ordering on output, but some do not. Definitely a bad order can make a huge difference in performance, both for cache traffic and conditioning reasons.
Also is there an example that uses Metis to partition an unstructured mesh?
This depends on what you mean. If you can encode your mesh as a Mat, you can use MatPartitoning. If not, you would need to use DMMesh things, such as SNES ex12. Matt
Thanks in advance.
Tabrez
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
if you want to use a general unstructured grid, you may want to have a look at $PETSC_DIR/src/dm/ao/examples/tutorials/ex2.c Mohammad On Thu, Aug 4, 2011 at 4:43 PM, Matthew Knepley <[email protected]> wrote:
On Thu, Aug 4, 2011 at 11:31 PM, Tabrez Ali <[email protected]>wrote:
Hello
If a mesh is partitioned using Metis but the original order of nodes is used to create/partition the matrix then would this be significantly bad for performance and scalability.
That depends. Many mesh generators h ave fairly good ordering on output, but some do not. Definitely a bad order can make a huge difference in performance, both for cache traffic and conditioning reasons.
Also is there an example that uses Metis to partition an unstructured mesh?
This depends on what you mean. If you can encode your mesh as a Mat, you can use MatPartitoning. If not, you would need to use DMMesh things, such as SNES ex12.
Matt
Thanks in advance.
Tabrez
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
DA: Sometimes I may encounter crashing when using PETSc, it doesn't happen always. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [0]PETSC ERROR: to get more information on the crash. [0]PETSC ERROR: --------------------- Error Message ------------------------------------ [0]PETSC ERROR: Signal received! [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17 13:37:48 CDT 2011 [0]PETSC ERROR: See docs/changes/index.html for recent updates. [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. [0]PETSC ERROR: See docs/index.html for manual pages. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Unknown Name on a linux-gnu named r0leaf17 by tachyon Thu Aug 4 04:04:19 2011 [0]PETSC ERROR: Libraries linked from /home/dshao/dev_t2k/third_party/OOQP/OOQP-0.99.19/extras/petsc-3.1-p8/linux-gnu-c-debug/lib [0]PETSC ERROR: Configure run at Thu Apr 21 18:09:19 2011 [0]PETSC ERROR: Configure options --with-mpi=0 --with-debugging=0 -with-log=0 -with-info=0 [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file Do you happen to know the possible cause? I also have a question about the usage of "PetscInitialize" & "PetscFinalize". I can't totally understand them from the manual. Now, I wrote it as: Int main(int argc, char **argv) { PetscInitialize(0, 0, 0, 0 ); VerifyApp app(argc, argv); app.Initialize(); app.Run(); PetscFinalize(); return 0; } Then, built a binary, say "verify", and executed "verify" on a server first, then, started another "verify" on client by server. The program ran at client side can be multiple processes and multiple threads. Is my usage correct? Your answer is appreciated. 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.
On Fri, Aug 5, 2011 at 2:20 AM, Debao Shao <[email protected]> wrote:
**
DA: ****
** **
Sometimes I may encounter crashing when using PETSc, it doesn’t happen always. ****
** **
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end****
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger ****
[0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSCERROR: or try http://valgrind.org on GNU/linux****
and Apple Mac OS X to find memory corruption errors****
[0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run****
[0]PETSC ERROR: to get more information on the crash.****
[0]PETSC ERROR: --------------------- Error Message ------------------------------------****
[0]PETSC ERROR: Signal received!****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17 13:37:48 CDT 2011****
[0]PETSC ERROR: See docs/changes/index.html for recent updates.****
[0]PETSC ERROR: See docs/faq.html for hints about trouble shooting.****
[0]PETSC ERROR: See docs/index.html for manual pages.****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: Unknown Name on a linux-gnu named r0leaf17 by tachyon Thu Aug 4 04:04:19 2011****
[0]PETSC ERROR: Libraries linked from /home/dshao/dev_t2k/third_party/OOQP/OOQP-0.99.19/extras/petsc-3.1-p8/linux-gnu-c-debug/lib ****
[0]PETSC ERROR: Configure run at Thu Apr 21 18:09:19 2011****
[0]PETSC ERROR: Configure options --with-mpi=0 --with-debugging=0 -with-log=0 -with-info=0****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file****
** **
Do you happen to know the possible cause?****
** **
I also have a question about the usage of “PetscInitialize” & “PetscFinalize”. I can’t totally understand them from the manual. ****
** **
Now, I wrote it as: ****
Int main(int argc, char **argv)****
{****
PetscInitialize(0, 0, 0, 0 );
This is not a valid call. Try PetscInitialize(&argc, &argv, 0, 0); Signal 15 is a segmentation fault, which means an illegal memory read or write. Matt
****
** **
VerifyApp app(argc, argv);****
app.Initialize();****
app.Run();****
** **
PetscFinalize();****
return 0;****
}****
** **
Then, built a binary, say “verify”, and executed “verify” on a server first, then, started another “verify” on client by server. ****
The program ran at client side can be multiple processes and multiple threads.****
** **
Is my usage correct? ****
Your answer is appreciated. ****
** **
Thanks,****
**De**bao****
------------------------------ -- 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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
So the real problem is the wrong usage of "PetscInitialize(0, 0, 0, 0 )", but I do have many successive runs before with this setting. Thanks, Debao ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Knepley Sent: Friday, August 05, 2011 10:25 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate On Fri, Aug 5, 2011 at 2:20 AM, Debao Shao <[email protected]<mailto:[email protected]>> wrote: DA: Sometimes I may encounter crashing when using PETSc, it doesn't happen always. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [0]PETSC ERROR: to get more information on the crash. [0]PETSC ERROR: --------------------- Error Message ------------------------------------ [0]PETSC ERROR: Signal received! [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17 13:37:48 CDT 2011 [0]PETSC ERROR: See docs/changes/index.html for recent updates. [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. [0]PETSC ERROR: See docs/index.html for manual pages. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Unknown Name on a linux-gnu named r0leaf17 by tachyon Thu Aug 4 04:04:19 2011 [0]PETSC ERROR: Libraries linked from /home/dshao/dev_t2k/third_party/OOQP/OOQP-0.99.19/extras/petsc-3.1-p8/linux-gnu-c-debug/lib [0]PETSC ERROR: Configure run at Thu Apr 21 18:09:19 2011 [0]PETSC ERROR: Configure options --with-mpi=0 --with-debugging=0 -with-log=0 -with-info=0 [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file Do you happen to know the possible cause? I also have a question about the usage of "PetscInitialize" & "PetscFinalize". I can't totally understand them from the manual. Now, I wrote it as: Int main(int argc, char **argv) { PetscInitialize(0, 0, 0, 0 ); This is not a valid call. Try PetscInitialize(&argc, &argv, 0, 0); Signal 15 is a segmentation fault, which means an illegal memory read or write. Matt VerifyApp app(argc, argv); app.Initialize(); app.Run(); PetscFinalize(); return 0; } Then, built a binary, say "verify", and executed "verify" on a server first, then, started another "verify" on client by server. The program ran at client side can be multiple processes and multiple threads. Is my usage correct? Your answer is appreciated. 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. -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener ________________________________ -- 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.
On Fri, Aug 5, 2011 at 2:33 AM, Debao Shao <[email protected]> wrote:
**
So the real problem is the wrong usage of “PetscInitialize(0, 0, 0, 0 )”, but I do have many successive runs before with this setting.
Any kind of memory overwrite gives an SEGV. So other code, making a different error will give that too. Matt
Thanks,****
**De**bao**** ------------------------------
*From:* [email protected] [mailto: [email protected]] *On Behalf Of *Matthew Knepley *Sent:* Friday, August 05, 2011 10:25 AM *To:* **PETSc users list** *Subject:* Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate****
** **
On Fri, Aug 5, 2011 at 2:20 AM, **De**bao Shao <[email protected]> wrote:****
DA: ****
****
Sometimes I may encounter crashing when using PETSc, it doesn’t happen always. ****
****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end****
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger ****
[0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSCERROR: or try http://valgrind.org on GNU/linux****
and Apple Mac OS X to find memory corruption errors****
[0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run****
[0]PETSC ERROR: to get more information on the crash.****
[0]PETSC ERROR: --------------------- Error Message ------------------------------------****
[0]PETSC ERROR: Signal received!****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17 13:37:48 CDT 2011****
[0]PETSC ERROR: See docs/changes/index.html for recent updates.****
[0]PETSC ERROR: See docs/faq.html for hints about trouble shooting.****
[0]PETSC ERROR: See docs/index.html for manual pages.****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: Unknown Name on a linux-gnu named r0leaf17 by tachyon Thu Aug 4 04:04:19 2011****
[0]PETSC ERROR: Libraries linked from /home/dshao/dev_t2k/third_party/OOQP/OOQP-0.99.19/extras/petsc-3.1-p8/linux-gnu-c-debug/lib ****
[0]PETSC ERROR: Configure run at Thu Apr 21 18:09:19 2011****
[0]PETSC ERROR: Configure options --with-mpi=0 --with-debugging=0 -with-log=0 -with-info=0****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file****
****
Do you happen to know the possible cause?****
****
I also have a question about the usage of “PetscInitialize” & “PetscFinalize”. I can’t totally understand them from the manual. ****
****
Now, I wrote it as: ****
Int main(int argc, char **argv)****
{****
PetscInitialize(0, 0, 0, 0 );****
** **
This is not a valid call. Try****
** **
PetscInitialize(&argc, &argv, 0, 0);****
** **
Signal 15 is a segmentation fault, which means an illegal memory read or write.****
** **
Matt****
****
****
VerifyApp app(argc, argv);****
app.Initialize();****
app.Run();****
****
PetscFinalize();****
return 0;****
}****
****
Then, built a binary, say “verify”, and executed “verify” on a server first, then, started another “verify” on client by server. ****
The program ran at client side can be multiple processes and multiple threads.****
****
Is my usage correct? ****
Your answer is appreciated. ****
****
Thanks,****
**De**bao****
** ** ------------------------------
-- 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.****
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener****
------------------------------ -- 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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
Doesn't SEGV fault is signal 11? ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Knepley Sent: Friday, August 05, 2011 10:35 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate On Fri, Aug 5, 2011 at 2:33 AM, Debao Shao <[email protected]<mailto:[email protected]>> wrote: So the real problem is the wrong usage of "PetscInitialize(0, 0, 0, 0 )", but I do have many successive runs before with this setting. Any kind of memory overwrite gives an SEGV. So other code, making a different error will give that too. Matt Thanks, Debao ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Matthew Knepley Sent: Friday, August 05, 2011 10:25 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate On Fri, Aug 5, 2011 at 2:20 AM, Debao Shao <[email protected]<mailto:[email protected]>> wrote: DA: Sometimes I may encounter crashing when using PETSc, it doesn't happen always. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [0]PETSC ERROR: to get more information on the crash. [0]PETSC ERROR: --------------------- Error Message ------------------------------------ [0]PETSC ERROR: Signal received! [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17 13:37:48 CDT 2011 [0]PETSC ERROR: See docs/changes/index.html for recent updates. [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. [0]PETSC ERROR: See docs/index.html for manual pages. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Unknown Name on a linux-gnu named r0leaf17 by tachyon Thu Aug 4 04:04:19 2011 [0]PETSC ERROR: Libraries linked from /home/dshao/dev_t2k/third_party/OOQP/OOQP-0.99.19/extras/petsc-3.1-p8/linux-gnu-c-debug/lib [0]PETSC ERROR: Configure run at Thu Apr 21 18:09:19 2011 [0]PETSC ERROR: Configure options --with-mpi=0 --with-debugging=0 -with-log=0 -with-info=0 [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file Do you happen to know the possible cause? I also have a question about the usage of "PetscInitialize" & "PetscFinalize". I can't totally understand them from the manual. Now, I wrote it as: Int main(int argc, char **argv) { PetscInitialize(0, 0, 0, 0 ); This is not a valid call. Try PetscInitialize(&argc, &argv, 0, 0); Signal 15 is a segmentation fault, which means an illegal memory read or write. Matt VerifyApp app(argc, argv); app.Initialize(); app.Run(); PetscFinalize(); return 0; } Then, built a binary, say "verify", and executed "verify" on a server first, then, started another "verify" on client by server. The program ran at client side can be multiple processes and multiple threads. Is my usage correct? Your answer is appreciated. 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. -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener ________________________________ -- 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. -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener ________________________________ -- 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.
On Aug 4, 2011, at 8:38 PM, Debao Shao wrote:
Doesn’t SEGV fault is signal 11?
Yes., 15 is a software terminate single sent from some other process hence the error message:
Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end
I've seen some batch systems send this single when they think you have run out of time. There may be other reasons as well. Do you get this right away or after a long time? Barry
From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Knepley Sent: Friday, August 05, 2011 10:35 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate
On Fri, Aug 5, 2011 at 2:33 AM, Debao Shao <[email protected]> wrote: So the real problem is the wrong usage of “PetscInitialize(0, 0, 0, 0 )”, but I do have many successive runs before with this setting.
Any kind of memory overwrite gives an SEGV. So other code, making a different error will give that too.
Matt
Thanks, Debao From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Knepley Sent: Friday, August 05, 2011 10:25 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate
On Fri, Aug 5, 2011 at 2:20 AM, Debao Shao <[email protected]> wrote: DA:
Sometimes I may encounter crashing when using PETSc, it doesn’t happen always.
[0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [0]PETSC ERROR: to get more information on the crash. [0]PETSC ERROR: --------------------- Error Message ------------------------------------ [0]PETSC ERROR: Signal received! [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17 13:37:48 CDT 2011 [0]PETSC ERROR: See docs/changes/index.html for recent updates. [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. [0]PETSC ERROR: See docs/index.html for manual pages. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Unknown Name on a linux-gnu named r0leaf17 by tachyon Thu Aug 4 04:04:19 2011 [0]PETSC ERROR: Libraries linked from /home/dshao/dev_t2k/third_party/OOQP/OOQP-0.99.19/extras/petsc-3.1-p8/linux-gnu-c-debug/lib [0]PETSC ERROR: Configure run at Thu Apr 21 18:09:19 2011 [0]PETSC ERROR: Configure options --with-mpi=0 --with-debugging=0 -with-log=0 -with-info=0 [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file
Do you happen to know the possible cause?
I also have a question about the usage of “PetscInitialize” & “PetscFinalize”. I can’t totally understand them from the manual.
Now, I wrote it as: Int main(int argc, char **argv) { PetscInitialize(0, 0, 0, 0 );
This is not a valid call. Try
PetscInitialize(&argc, &argv, 0, 0);
Signal 15 is a segmentation fault, which means an illegal memory read or write.
Matt
VerifyApp app(argc, argv); app.Initialize(); app.Run();
PetscFinalize(); return 0; }
Then, built a binary, say “verify”, and executed “verify” on a server first, then, started another “verify” on client by server. The program ran at client side can be multiple processes and multiple threads.
Is my usage correct? Your answer is appreciated.
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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
-- 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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
-- 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 get this error after a long process. For example, I have 4 jobs to do, the program may crash after done 1 job or 2, 3, 4 jobs. Also, sometimes, the program can run finished successfully. Thanks, Debao -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Barry Smith Sent: Friday, August 05, 2011 10:43 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate On Aug 4, 2011, at 8:38 PM, Debao Shao wrote:
Doesn't SEGV fault is signal 11?
Yes., 15 is a software terminate single sent from some other process hence the error message:
Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end
I've seen some batch systems send this single when they think you have run out of time. There may be other reasons as well. Do you get this right away or after a long time? Barry
From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Knepley Sent: Friday, August 05, 2011 10:35 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate
On Fri, Aug 5, 2011 at 2:33 AM, Debao Shao <[email protected]> wrote: So the real problem is the wrong usage of "PetscInitialize(0, 0, 0, 0 )", but I do have many successive runs before with this setting.
Any kind of memory overwrite gives an SEGV. So other code, making a different error will give that too.
Matt
Thanks, Debao From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Knepley Sent: Friday, August 05, 2011 10:25 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate
On Fri, Aug 5, 2011 at 2:20 AM, Debao Shao <[email protected]> wrote: DA:
Sometimes I may encounter crashing when using PETSc, it doesn't happen always.
[0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [0]PETSC ERROR: to get more information on the crash. [0]PETSC ERROR: --------------------- Error Message ------------------------------------ [0]PETSC ERROR: Signal received! [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17 13:37:48 CDT 2011 [0]PETSC ERROR: See docs/changes/index.html for recent updates. [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. [0]PETSC ERROR: See docs/index.html for manual pages. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Unknown Name on a linux-gnu named r0leaf17 by tachyon Thu Aug 4 04:04:19 2011 [0]PETSC ERROR: Libraries linked from /home/dshao/dev_t2k/third_party/OOQP/OOQP-0.99.19/extras/petsc-3.1-p8/linux-gnu-c-debug/lib [0]PETSC ERROR: Configure run at Thu Apr 21 18:09:19 2011 [0]PETSC ERROR: Configure options --with-mpi=0 --with-debugging=0 -with-log=0 -with-info=0 [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file
Do you happen to know the possible cause?
I also have a question about the usage of "PetscInitialize" & "PetscFinalize". I can't totally understand them from the manual.
Now, I wrote it as: Int main(int argc, char **argv) { PetscInitialize(0, 0, 0, 0 );
This is not a valid call. Try
PetscInitialize(&argc, &argv, 0, 0);
Signal 15 is a segmentation fault, which means an illegal memory read or write.
Matt
VerifyApp app(argc, argv); app.Initialize(); app.Run();
PetscFinalize(); return 0; }
Then, built a binary, say "verify", and executed "verify" on a server first, then, started another "verify" on client by server. The program ran at client side can be multiple processes and multiple threads.
Is my usage correct? Your answer is appreciated.
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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
-- 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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
-- 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.
On Fri, Aug 5, 2011 at 2:54 AM, Debao Shao <[email protected]> wrote:
I get this error after a long process. For example, I have 4 jobs to do, the program may crash after done 1 job or 2, 3, 4 jobs. Also, sometimes, the program can run finished successfully.
This sounds like your system has a time limit (maybe ulimit) for jobs and kills your when they run too long. Matt
Thanks, Debao
-----Original Message----- From: [email protected] [mailto: [email protected]] On Behalf Of Barry Smith Sent: Friday, August 05, 2011 10:43 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate
On Aug 4, 2011, at 8:38 PM, Debao Shao wrote:
Doesn't SEGV fault is signal 11?
Yes., 15 is a software terminate single sent from some other process hence the error message:
Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end
I've seen some batch systems send this single when they think you have run out of time. There may be other reasons as well. Do you get this right away or after a long time?
Barry
From: [email protected] [mailto:
[email protected]] On Behalf Of Matthew Knepley
Sent: Friday, August 05, 2011 10:35 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate
On Fri, Aug 5, 2011 at 2:33 AM, Debao Shao <[email protected]> wrote: So the real problem is the wrong usage of "PetscInitialize(0, 0, 0, 0 )", but I do have many successive runs before with this setting.
Any kind of memory overwrite gives an SEGV. So other code, making a different error will give that too.
Matt
Thanks, Debao From: [email protected] [mailto: [email protected]] On Behalf Of Matthew Knepley Sent: Friday, August 05, 2011 10:25 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate
On Fri, Aug 5, 2011 at 2:20 AM, Debao Shao <[email protected]> wrote: DA:
Sometimes I may encounter crashing when using PETSc, it doesn't happen always.
[0]PETSC ERROR:
[0]PETSC ERROR: Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSCERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [0]PETSC ERROR: to get more information on the crash. [0]PETSC ERROR: --------------------- Error Message
[0]PETSC ERROR: Signal received! [0]PETSC ERROR:
[0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17 13:37:48 CDT 2011 [0]PETSC ERROR: See docs/changes/index.html for recent updates. [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. [0]PETSC ERROR: See docs/index.html for manual pages. [0]PETSC ERROR:
[0]PETSC ERROR: Unknown Name on a linux-gnu named r0leaf17 by tachyon Thu Aug 4 04:04:19 2011 [0]PETSC ERROR: Libraries linked from /home/dshao/dev_t2k/third_party/OOQP/OOQP-0.99.19/extras/petsc-3.1-p8/linux-gnu-c-debug/lib [0]PETSC ERROR: Configure run at Thu Apr 21 18:09:19 2011 [0]PETSC ERROR: Configure options --with-mpi=0 --with-debugging=0 -with-log=0 -with-info=0 [0]PETSC ERROR:
[0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file
Do you happen to know the possible cause?
I also have a question about the usage of "PetscInitialize" & "PetscFinalize". I can't totally understand them from the manual.
Now, I wrote it as: Int main(int argc, char **argv) { PetscInitialize(0, 0, 0, 0 );
This is not a valid call. Try
PetscInitialize(&argc, &argv, 0, 0);
Signal 15 is a segmentation fault, which means an illegal memory read or write.
Matt
VerifyApp app(argc, argv); app.Initialize(); app.Run();
PetscFinalize(); return 0; }
Then, built a binary, say "verify", and executed "verify" on a server first, then, started another "verify" on client by server. The program ran at client side can be multiple processes and multiple threads.
Is my usage correct? Your answer is appreciated.
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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
-- 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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
-- 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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
On Aug 4, 2011, at 8:54 PM, Debao Shao wrote:
I get this error after a long process. For example, I have 4 jobs to do, the program may crash after done 1 job or 2, 3, 4 jobs. Also, sometimes, the program can run finished successfully.
The program is not crashing. The batch system is kicking out the job, probably because it thinks it has run out of time. You'll need to set a longer time for the batch system. Barry
Thanks, Debao
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Barry Smith Sent: Friday, August 05, 2011 10:43 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate
On Aug 4, 2011, at 8:38 PM, Debao Shao wrote:
Doesn't SEGV fault is signal 11?
Yes., 15 is a software terminate single sent from some other process hence the error message:
Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end
I've seen some batch systems send this single when they think you have run out of time. There may be other reasons as well. Do you get this right away or after a long time?
Barry
From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Knepley Sent: Friday, August 05, 2011 10:35 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate
On Fri, Aug 5, 2011 at 2:33 AM, Debao Shao <[email protected]> wrote: So the real problem is the wrong usage of "PetscInitialize(0, 0, 0, 0 )", but I do have many successive runs before with this setting.
Any kind of memory overwrite gives an SEGV. So other code, making a different error will give that too.
Matt
Thanks, Debao From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Knepley Sent: Friday, August 05, 2011 10:25 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate
On Fri, Aug 5, 2011 at 2:20 AM, Debao Shao <[email protected]> wrote: DA:
Sometimes I may encounter crashing when using PETSc, it doesn't happen always.
[0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [0]PETSC ERROR: to get more information on the crash. [0]PETSC ERROR: --------------------- Error Message ------------------------------------ [0]PETSC ERROR: Signal received! [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17 13:37:48 CDT 2011 [0]PETSC ERROR: See docs/changes/index.html for recent updates. [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. [0]PETSC ERROR: See docs/index.html for manual pages. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Unknown Name on a linux-gnu named r0leaf17 by tachyon Thu Aug 4 04:04:19 2011 [0]PETSC ERROR: Libraries linked from /home/dshao/dev_t2k/third_party/OOQP/OOQP-0.99.19/extras/petsc-3.1-p8/linux-gnu-c-debug/lib [0]PETSC ERROR: Configure run at Thu Apr 21 18:09:19 2011 [0]PETSC ERROR: Configure options --with-mpi=0 --with-debugging=0 -with-log=0 -with-info=0 [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file
Do you happen to know the possible cause?
I also have a question about the usage of "PetscInitialize" & "PetscFinalize". I can't totally understand them from the manual.
Now, I wrote it as: Int main(int argc, char **argv) { PetscInitialize(0, 0, 0, 0 );
This is not a valid call. Try
PetscInitialize(&argc, &argv, 0, 0);
Signal 15 is a segmentation fault, which means an illegal memory read or write.
Matt
VerifyApp app(argc, argv); app.Initialize(); app.Run();
PetscFinalize(); return 0; }
Then, built a binary, say "verify", and executed "verify" on a server first, then, started another "verify" on client by server. The program ran at client side can be multiple processes and multiple threads.
Is my usage correct? Your answer is appreciated.
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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
-- 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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
-- 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.
Thanks a lot, Barry and Matthew. I found the root cause of my problem. 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. With changing the position of "PetscInitialize", I fixed the issue. 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? Please give your comments, thanks a lot. Regards, Debao -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Barry Smith Sent: Friday, August 05, 2011 10:57 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate On Aug 4, 2011, at 8:54 PM, Debao Shao wrote:
I get this error after a long process.
For example, I have 4 jobs to do, the program may crash after done 1 job or 2, 3, 4 jobs. Also, sometimes, the program can run finished successfully.
The program is not crashing. The batch system is kicking out the job, probably because it thinks it has run out of time. You'll need to set a longer time for the batch system. Barry
Thanks,
Debao
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Barry Smith
Sent: Friday, August 05, 2011 10:43 AM
To: PETSc users list
Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate
On Aug 4, 2011, at 8:38 PM, Debao Shao wrote:
Doesn't SEGV fault is signal 11?
Yes., 15 is a software terminate single sent from some other process hence the error message:
Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end
I've seen some batch systems send this single when they think you have run out of time. There may be other reasons as well. Do you get this right away or after a long time?
Barry
From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Knepley
Sent: Friday, August 05, 2011 10:35 AM
To: PETSc users list
Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate
On Fri, Aug 5, 2011 at 2:33 AM, Debao Shao <[email protected]> wrote:
So the real problem is the wrong usage of "PetscInitialize(0, 0, 0, 0 )", but I do have many successive runs before with this setting.
Any kind of memory overwrite gives an SEGV. So other code, making a different error will give that too.
Matt
Thanks,
Debao
From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Knepley
Sent: Friday, August 05, 2011 10:25 AM
To: PETSc users list
Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate
On Fri, Aug 5, 2011 at 2:20 AM, Debao Shao <[email protected]> wrote:
DA:
Sometimes I may encounter crashing when using PETSc, it doesn't happen always.
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC ERROR: or try http://valgrind.org on GNU/linux
and Apple Mac OS X to find memory corruption errors
[0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run
[0]PETSC ERROR: to get more information on the crash.
[0]PETSC ERROR: --------------------- Error Message ------------------------------------
[0]PETSC ERROR: Signal received!
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17 13:37:48 CDT 2011
[0]PETSC ERROR: See docs/changes/index.html for recent updates.
[0]PETSC ERROR: See docs/faq.html for hints about trouble shooting.
[0]PETSC ERROR: See docs/index.html for manual pages.
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Unknown Name on a linux-gnu named r0leaf17 by tachyon Thu Aug 4 04:04:19 2011
[0]PETSC ERROR: Libraries linked from /home/dshao/dev_t2k/third_party/OOQP/OOQP-0.99.19/extras/petsc-3.1-p8/linux-gnu-c-debug/lib
[0]PETSC ERROR: Configure run at Thu Apr 21 18:09:19 2011
[0]PETSC ERROR: Configure options --with-mpi=0 --with-debugging=0 -with-log=0 -with-info=0
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file
Do you happen to know the possible cause?
I also have a question about the usage of "PetscInitialize" & "PetscFinalize". I can't totally understand them from the manual.
Now, I wrote it as:
Int main(int argc, char **argv)
{
PetscInitialize(0, 0, 0, 0 );
This is not a valid call. Try
PetscInitialize(&argc, &argv, 0, 0);
Signal 15 is a segmentation fault, which means an illegal memory read or write.
Matt
VerifyApp app(argc, argv);
app.Initialize();
app.Run();
PetscFinalize();
return 0;
}
Then, built a binary, say "verify", and executed "verify" on a server first, then, started another "verify" on client by server.
The program ran at client side can be multiple processes and multiple threads.
Is my usage correct?
Your answer is appreciated.
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.
--
What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
-- Norbert Wiener
-- 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.
--
What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
-- Norbert Wiener
-- 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.
"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."**** You should be using PETSc+MPI to handle this distribution for you. Threading will not get around any memory limits for a single process that your system may have. A
On Fri, Aug 5, 2011 at 04:00, Debao Shao <[email protected]> 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/S...
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: [email protected] [mailto:[email protected]] 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 <[email protected]<mailto:[email protected]>> 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/S... ________________________________ -- 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.
On Sat, Aug 6, 2011 at 1:34 AM, Debao Shao <[email protected]> wrote:
**
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**"
Yes, PETSc allows threads, but one of your threads is illegally accessing memory. I suggest using valgrind to track this down. Matt
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,****
**De**bao**** ------------------------------
*From:* [email protected] [mailto: [email protected]] *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, **De**bao Shao <[email protected]> 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/S... ****
------------------------------ -- 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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
Hi, Matt: http://www.mcs.anl.gov/petsc/petsc-as/miscellaneous/petscthreads.html says "PETSc is not currently thread-safe". And, you said "PETSc allows threads", I was confused, can you explain a little for me? Thanks a lot. Debao ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Knepley Sent: Saturday, August 06, 2011 11:19 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate On Sat, Aug 6, 2011 at 1:34 AM, Debao Shao <[email protected]<mailto:[email protected]>> wrote: 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" Yes, PETSc allows threads, but one of your threads is illegally accessing memory. I suggest using valgrind to track this down. Matt 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: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] 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 <[email protected]<mailto:[email protected]>> 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/S... ________________________________ -- 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. -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener ________________________________ -- 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.
On Tue, Aug 9, 2011 at 10:36 PM, Debao Shao <[email protected]> wrote:
Hi, Matt: ****
** **
http://www.mcs.anl.gov/petsc/petsc-as/miscellaneous/petscthreads.html says “PETSc is not currently thread-safe”.****
And, you said “PETSc allows threads”, I was confused, can you explain a little for me?
You are not prevented from using threads, but PETSc data structures are not thread-safe (we do nothing with threads). By allow, I meant you can do whatever you want, but we do not supported a threaded model. Sorry it was not clear. Matt
Thanks a lot. ****
** **
Debao **** ------------------------------
*From:* [email protected] [mailto: [email protected]] *On Behalf Of *Matthew Knepley *Sent:* Saturday, August 06, 2011 11:19 AM
*To:* PETSc users list *Subject:* Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate ****
** **
On Sat, Aug 6, 2011 at 1:34 AM, Debao Shao <[email protected]> wrote:** **
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"****
** **
Yes, PETSc allows threads, but one of your threads is illegally accessing memory. I suggest using valgrind to track this down.****
** **
Matt****
****
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:* [email protected] [mailto: [email protected]] *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 <[email protected]> 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/S... ****
** ** ------------------------------
-- 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.****
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener****
------------------------------ -- 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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
Ok, I see. Thanks a lot. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Knepley Sent: Wednesday, August 10, 2011 11:43 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate On Tue, Aug 9, 2011 at 10:36 PM, Debao Shao <[email protected]<mailto:[email protected]>> wrote: Hi, Matt: http://www.mcs.anl.gov/petsc/petsc-as/miscellaneous/petscthreads.html says "PETSc is not currently thread-safe". And, you said "PETSc allows threads", I was confused, can you explain a little for me? You are not prevented from using threads, but PETSc data structures are not thread-safe (we do nothing with threads). By allow, I meant you can do whatever you want, but we do not supported a threaded model. Sorry it was not clear. Matt Thanks a lot. Debao ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Matthew Knepley Sent: Saturday, August 06, 2011 11:19 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate On Sat, Aug 6, 2011 at 1:34 AM, Debao Shao <[email protected]<mailto:[email protected]>> wrote: 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" Yes, PETSc allows threads, but one of your threads is illegally accessing memory. I suggest using valgrind to track this down. Matt 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: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] 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 <[email protected]<mailto:[email protected]>> 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/S... ________________________________ -- 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. -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener ________________________________ -- 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. -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener ________________________________ -- 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.
On Fri, Aug 5, 2011 at 2:38 AM, Debao Shao <[email protected]> wrote:
**
Doesn’t SEGV fault is signal 11?
Yes, 15 is SIGTERM. It appears that either you have another signal handler installed which is terminating on an error, or something killed your program. I can guarantee you that the PetscInitialize(0,0,0,0) is a seg fault. Matt
------------------------------
*From:* [email protected] [mailto: [email protected]] *On Behalf Of *Matthew Knepley *Sent:* Friday, August 05, 2011 10:35 AM
*To:* **PETSc users list** *Subject:* Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate ****
** **
On Fri, Aug 5, 2011 at 2:33 AM, **De**bao Shao <[email protected]> wrote:****
So the real problem is the wrong usage of “PetscInitialize(0, 0, 0, 0 )”, but I do have many successive runs before with this setting.****
** **
Any kind of memory overwrite gives an SEGV. So other code, making a different error will give that too.****
** **
Matt****
****
****
Thanks,****
**De**bao**** ------------------------------
*From:* [email protected] [mailto: [email protected]] *On Behalf Of *Matthew Knepley *Sent:* Friday, August 05, 2011 10:25 AM *To:* **PETSc users list** *Subject:* Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate****
****
On Fri, Aug 5, 2011 at 2:20 AM, **De**bao Shao <[email protected]> wrote:****
DA: ****
****
Sometimes I may encounter crashing when using PETSc, it doesn’t happen always. ****
****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end****
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger ****
[0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSCERROR: or try http://valgrind.org on GNU/linux****
and Apple Mac OS X to find memory corruption errors****
[0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run****
[0]PETSC ERROR: to get more information on the crash.****
[0]PETSC ERROR: --------------------- Error Message ------------------------------------****
[0]PETSC ERROR: Signal received!****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17 13:37:48 CDT 2011****
[0]PETSC ERROR: See docs/changes/index.html for recent updates.****
[0]PETSC ERROR: See docs/faq.html for hints about trouble shooting.****
[0]PETSC ERROR: See docs/index.html for manual pages.****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: Unknown Name on a linux-gnu named r0leaf17 by tachyon Thu Aug 4 04:04:19 2011****
[0]PETSC ERROR: Libraries linked from /home/dshao/dev_t2k/third_party/OOQP/OOQP-0.99.19/extras/petsc-3.1-p8/linux-gnu-c-debug/lib ****
[0]PETSC ERROR: Configure run at Thu Apr 21 18:09:19 2011****
[0]PETSC ERROR: Configure options --with-mpi=0 --with-debugging=0 -with-log=0 -with-info=0****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file****
****
Do you happen to know the possible cause?****
****
I also have a question about the usage of “PetscInitialize” & “PetscFinalize”. I can’t totally understand them from the manual. ****
****
Now, I wrote it as: ****
Int main(int argc, char **argv)****
{****
PetscInitialize(0, 0, 0, 0 );****
****
This is not a valid call. Try****
****
PetscInitialize(&argc, &argv, 0, 0);****
****
Signal 15 is a segmentation fault, which means an illegal memory read or write.****
****
Matt****
****
****
VerifyApp app(argc, argv);****
app.Initialize();****
app.Run();****
****
PetscFinalize();****
return 0;****
}****
****
Then, built a binary, say “verify”, and executed “verify” on a server first, then, started another “verify” on client by server. ****
The program ran at client side can be multiple processes and multiple threads.****
****
Is my usage correct? ****
Your answer is appreciated. ****
****
Thanks,****
**De**bao****
**** ------------------------------
-- 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.****
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener****
** ** ------------------------------
-- 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.****
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener****
------------------------------ -- 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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
Thanks, I'm trying your suggestion "PetscInitialize(&argc, &argv, 0, 0 )", hope it can fix the problem. Do you mind to explain a little "PetscInitialize" to me? 1, must it be call at the beginning of program? 2, what's the other purpose if I don't want to input any argc? 3, if I implement petsc as an optional solution, can I put "PetscInitialize" just before petsc is really executed, while not just put them at the beginning of program? Thanks, Debao ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Knepley Sent: Friday, August 05, 2011 10:44 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate On Fri, Aug 5, 2011 at 2:38 AM, Debao Shao <[email protected]<mailto:[email protected]>> wrote: Doesn't SEGV fault is signal 11? Yes, 15 is SIGTERM. It appears that either you have another signal handler installed which is terminating on an error, or something killed your program. I can guarantee you that the PetscInitialize(0,0,0,0) is a seg fault. Matt ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Matthew Knepley Sent: Friday, August 05, 2011 10:35 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate On Fri, Aug 5, 2011 at 2:33 AM, Debao Shao <[email protected]<mailto:[email protected]>> wrote: So the real problem is the wrong usage of "PetscInitialize(0, 0, 0, 0 )", but I do have many successive runs before with this setting. Any kind of memory overwrite gives an SEGV. So other code, making a different error will give that too. Matt Thanks, Debao ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Matthew Knepley Sent: Friday, August 05, 2011 10:25 AM To: PETSc users list Subject: Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate On Fri, Aug 5, 2011 at 2:20 AM, Debao Shao <[email protected]<mailto:[email protected]>> wrote: DA: Sometimes I may encounter crashing when using PETSc, it doesn't happen always. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [0]PETSC ERROR: to get more information on the crash. [0]PETSC ERROR: --------------------- Error Message ------------------------------------ [0]PETSC ERROR: Signal received! [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17 13:37:48 CDT 2011 [0]PETSC ERROR: See docs/changes/index.html for recent updates. [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. [0]PETSC ERROR: See docs/index.html for manual pages. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Unknown Name on a linux-gnu named r0leaf17 by tachyon Thu Aug 4 04:04:19 2011 [0]PETSC ERROR: Libraries linked from /home/dshao/dev_t2k/third_party/OOQP/OOQP-0.99.19/extras/petsc-3.1-p8/linux-gnu-c-debug/lib [0]PETSC ERROR: Configure run at Thu Apr 21 18:09:19 2011 [0]PETSC ERROR: Configure options --with-mpi=0 --with-debugging=0 -with-log=0 -with-info=0 [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file Do you happen to know the possible cause? I also have a question about the usage of "PetscInitialize" & "PetscFinalize". I can't totally understand them from the manual. Now, I wrote it as: Int main(int argc, char **argv) { PetscInitialize(0, 0, 0, 0 ); This is not a valid call. Try PetscInitialize(&argc, &argv, 0, 0); Signal 15 is a segmentation fault, which means an illegal memory read or write. Matt VerifyApp app(argc, argv); app.Initialize(); app.Run(); PetscFinalize(); return 0; } Then, built a binary, say "verify", and executed "verify" on a server first, then, started another "verify" on client by server. The program ran at client side can be multiple processes and multiple threads. Is my usage correct? Your answer is appreciated. 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. -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener ________________________________ -- 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. -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener ________________________________ -- 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. -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener ________________________________ -- 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.
On Fri, Aug 5, 2011 at 2:50 AM, Debao Shao <[email protected]> wrote:
**
Thanks, I’m trying your suggestion “PetscInitialize(&argc, &argv, 0, 0 )”, hope it can fix the problem. ****
** **
Do you mind to explain a little “PetscInitialize” to me? ****
1, must it be call at the beginning of program?
It must be called before you call any PETSc function, or use MPI.
****
2, what’s the other purpose if I don’t want to input any argc?
It initializes MPI.
****
3, if I implement petsc as an optional solution, can I put “PetscInitialize” just before petsc is really executed, while not just put them at the beginning of program?
Yes. Matt
Thanks,****
**De**bao**** ------------------------------
*From:* [email protected] [mailto: [email protected]] *On Behalf Of *Matthew Knepley *Sent:* Friday, August 05, 2011 10:44 AM *To:* **PETSc users list** *Subject:* Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate****
** **
On Fri, Aug 5, 2011 at 2:38 AM, **De**bao Shao <[email protected]> wrote:****
Doesn’t SEGV fault is signal 11?****
** **
Yes, 15 is SIGTERM. It appears that either you have another signal handler installed which****
is terminating on an error, or something killed your program. I can guarantee you that the****
PetscInitialize(0,0,0,0) is a seg fault.****
** **
Matt****
****
**** ------------------------------
*From:* [email protected] [mailto: [email protected]] *On Behalf Of *Matthew Knepley *Sent:* Friday, August 05, 2011 10:35 AM****
*To:* **PETSc users list** *Subject:* Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate****
****
On Fri, Aug 5, 2011 at 2:33 AM, **De**bao Shao <[email protected]> wrote:****
So the real problem is the wrong usage of “PetscInitialize(0, 0, 0, 0 )”, but I do have many successive runs before with this setting.****
****
Any kind of memory overwrite gives an SEGV. So other code, making a different error will give that too.****
****
Matt****
****
****
Thanks,****
**De**bao**** ------------------------------
*From:* [email protected] [mailto: [email protected]] *On Behalf Of *Matthew Knepley *Sent:* Friday, August 05, 2011 10:25 AM *To:* **PETSc users list** *Subject:* Re: [petsc-users] PETSC ERROR: Caught signal number 15 Terminate****
****
On Fri, Aug 5, 2011 at 2:20 AM, **De**bao Shao <[email protected]> wrote:****
DA: ****
****
Sometimes I may encounter crashing when using PETSc, it doesn’t happen always. ****
****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: Caught signal number 15 Terminate: Somet process (or the batch system) has told this process to end****
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger ****
[0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSCERROR: or try http://valgrind.org on GNU/linux****
and Apple Mac OS X to find memory corruption errors****
[0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run****
[0]PETSC ERROR: to get more information on the crash.****
[0]PETSC ERROR: --------------------- Error Message ------------------------------------****
[0]PETSC ERROR: Signal received!****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17 13:37:48 CDT 2011****
[0]PETSC ERROR: See docs/changes/index.html for recent updates.****
[0]PETSC ERROR: See docs/faq.html for hints about trouble shooting.****
[0]PETSC ERROR: See docs/index.html for manual pages.****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: Unknown Name on a linux-gnu named r0leaf17 by tachyon Thu Aug 4 04:04:19 2011****
[0]PETSC ERROR: Libraries linked from /home/dshao/dev_t2k/third_party/OOQP/OOQP-0.99.19/extras/petsc-3.1-p8/linux-gnu-c-debug/lib ****
[0]PETSC ERROR: Configure run at Thu Apr 21 18:09:19 2011****
[0]PETSC ERROR: Configure options --with-mpi=0 --with-debugging=0 -with-log=0 -with-info=0****
[0]PETSC ERROR: ------------------------------------------------------------------------** **
[0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file****
****
Do you happen to know the possible cause?****
****
I also have a question about the usage of “PetscInitialize” & “PetscFinalize”. I can’t totally understand them from the manual. ****
****
Now, I wrote it as: ****
Int main(int argc, char **argv)****
{****
PetscInitialize(0, 0, 0, 0 );****
****
This is not a valid call. Try****
****
PetscInitialize(&argc, &argv, 0, 0);****
****
Signal 15 is a segmentation fault, which means an illegal memory read or write.****
****
Matt****
****
****
VerifyApp app(argc, argv);****
app.Initialize();****
app.Run();****
****
PetscFinalize();****
return 0;****
}****
****
Then, built a binary, say “verify”, and executed “verify” on a server first, then, started another “verify” on client by server. ****
The program ran at client side can be multiple processes and multiple threads.****
****
Is my usage correct? ****
Your answer is appreciated. ****
****
Thanks,****
**De**bao****
**** ------------------------------
-- 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.****
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener****
**** ------------------------------
-- 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.****
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener****
** ** ------------------------------
-- 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.****
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener****
------------------------------ -- 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.
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
participants (7)
-
Aron Ahmadia -
Barry Smith -
Debao Shao -
Jed Brown -
Matthew Knepley -
Mohammad Mirzadeh -
Tabrez Ali