[Octopus-users] Segmentation fault(contd)
xavier at tddft.org
Wed Nov 30 12:40:43 WET 2005
Have you tried to erase the old restart files ( rm -r tmp/ ) before doing
the new run with different spacing? In my experience, sometimes octopus gets
confused with that.
On Wed, 30 Nov 2005, A Sen wrote:
> Dear Roberto and Giacomo,
> Even after typing "ulimit -s unlimited",the
> following problem (while reducing the mesh
>  + Segmentation fault octopus > out (core dumped)
> still persists.
> Ours is a 64-bit Itanium architecture on a Redhat Enterprise Linux
> platform with Intel compilers.
> Following are the various sizes in our set-up:
> core file size (blocks, -c) unlimited
> data seg size (kbytes, -d) unlimited
> file size (blocks, -f) unlimited
> max locked memory (kbytes, -l) 16
> max memory size (kbytes, -m) unlimited
> open files (-n) 1024
> pipe size (512 bytes, -p) 8
> stack size (kbytes, -s) unlimited
> cpu time (seconds, -t) unlimited
> max user processes (-u) 16339
> virtual memory (kbytes, -v) unlimited
> Should I relax any/some of these? If so, could you please suggest me what
> to type in the command line?
> Since ours is Intel compiler based Itanium64, I even failed to configure
> valgrind 3.1.0.in it. Perhaps valgrind does not work here.I therefore
> could not see whether some leaks and/or uses of unallocated memory are
> there or not.
> I carried out similar calculations for C6H6, but succeeded again only with
> the mesh spacing of 0.4 (and certainly not with 0.22 as given in the
> manual,which shows again "core dumped").
> I would be extremely grateful if you kindly suggest me what to do next
> with our limited resources.
> Octopus-users mailing list
> Octopus-users at tddft.org
More information about the Octopus-users