Skip to Content.
Sympa Menu

forum - Re: [abinit-forum] forrtl: severe (174): SIGSEGV, segmentation fault occurred

forum@abinit.org

Subject: The ABINIT Users Mailing List ( CLOSED )

List archive

Re: [abinit-forum] forrtl: severe (174): SIGSEGV, segmentation fault occurred


Chronological Thread 
  • From: Anglade Pierre-Matthieu <anglade@gmail.com>
  • To: forum@abinit.org
  • Subject: Re: [abinit-forum] forrtl: severe (174): SIGSEGV, segmentation fault occurred
  • Date: Wed, 16 Dec 2009 17:12:05 +0100
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=xRJ+fOihQ/o93/lVk2XSRb2VLSDyKKDSuHd0UqDBRNku3J5OALJbthI+PK1QZ6m0vp qseikTnFUdWqSrpjsmSQ4nUInCMeG7oBlbvmJCTXDZFqiBDZfz/LTvyop15ZfDRVz3St Dp/5ZV76kI6gii+yiuffuCT+jv+bqX//85WyI=

Hi,

Unfortunately, I may not be able to be very helpful.
Since your calculation works with ngkpt 60 60 60, it looks like the
segfault you observe is likely linked to the number of kpt used. So
far I guess we can not say much more than that.
Knowing exactly what is going on inside the code at the segfault
moment would likely give you (and us) more information on what shall
be corrected. If you have the possibility to do so, could you compile
the code again but with debug flags enabled ? And then run your
calculation monitoring each process with a debugger ? Finally when a
process fail, you would be able to backtrace the events and find what
exactly has caused the segmentation violation.

For instance, you would do the following :
configure --enable-debug
make
mpirun -np xxx abinit ....
top or ps -u login to get the PID of each parallel process launched
(on each used node of your cluster)
gdb abinit PID (on each node again)
bt

regards

PMA

On Wed, Dec 16, 2009 at 4:38 PM, haiou <haiouwyj@gmail.com> wrote:
> Can anybody help me ?
>



--
Pierre-Matthieu Anglade



Archive powered by MHonArc 2.6.16.

Top of Page