[CPMD-list] segmentation fault occurred

Axel Kohlmeyer akohlmey at cmm.chem.upenn.edu
Wed Apr 2 13:23:10 CEST 2008


On Wed, 2 Apr 2008, ê°½ðÁ¼ wrote:

A> Dear all,dear Axel

dear allen,

A> i am a abecedarian for cpmd. 

...and in proper problem reporting.
 
if you don't describe your problem in a way, so that somebody
can reproduce it, you will force people to guess or give you
incorrect answers, if any at all. have a look at, e.g.:

http://www.catb.org/~esr/faqs/smart-questions.html


A> nowdays, i just do the "4 DAY"exercises ,and want to learn how to use 

"4 DAY" exercise from where?? 

A> cpmd for a md calculation. when i come to "DAY3", an error occured. 
A> the inp3 's content is 

this is a properties run and has nothing to do with MD. 
what is the connection?

[...]

A>   i finished the inp1,inp2 smoothly,but when it comes to inp3,the 
A>   programe stopped, giving me following information, "forrtl: severe 
A>   (174): SIGSEGV, segmentation fault occurred
A> Image              PC                Routine            Line        Source             
A> cpmd311            000000000063A05E  Unknown               Unknown  Unknown

this is completely useless. the important information is the 
few last lines of the output _before_ the segfault occurs.
better yet. compile CPMD with debug info, generate a core dump
and find out, _where_ the code crashes. 

A> cpmd311            0000000000403ACC  Unknown               Unknown  Unknown
A> cpmd311            0000000000403666  Unknown               Unknown  Unknown
A> cpmd311            000000000040362A  Unknown               Unknown  Unknown
A> Unknown            0000003CC0C1C3FB  Unknown              Unknown  Unknown
A> cpmd311            000000000040356A  Unknown               Unknown  Unknown
A>  "

A> i met this problem" segmentation fault occurred " several times before. 
A> how can i to deal with  it?

first of all, you should do some research (google!, wikipedia!!)
to understand what a segfault is. then you should note that this
can have many reasons (bug in program, compiler bug, faulty memory,
faulty cpu cooling, ...) so you have to narrow it down to whether
it is reproducable and how it can be reproduced in the most simple
way. since you seem to be using an intel compiler (which version,
which platform, etc. etc.) it is possible, that you are running out
of stack memory and that you have to either recompile your code with
the compiler flag to use the heap instead of stack for automatic
arrays (read the compiler docs!) or increase the allowed stacksize
with ulimit/limit, but that is just a wild guess...

cheers,
   axel.

A> thanks!
A>   Allen
A> 
A> 
A> 
A>        
A> ---------------------------------
A>  ÑÅ»¢ÓÊÏ䣬ÄúµÄÖÕÉúÓÊÏ䣡

-- 
=======================================================================
Axel Kohlmeyer   akohlmey at cmm.chem.upenn.edu   http://www.cmm.upenn.edu
   Center for Molecular Modeling   --   University of Pennsylvania
Department of Chemistry, 231 S.34th Street, Philadelphia, PA 19104-6323
tel: 1-215-898-1582,  fax: 1-215-573-6233,  office-tel: 1-215-898-5425
=======================================================================
If you make something idiot-proof, the universe creates a better idiot.


More information about the CPMD-list mailing list