[Octopus-users] Segmentation fault(contd)

[Giacomo Mulas]

On Wed, 30 Nov 2005, A Sen wrote:

> Should I relax any/some of these?

Try relaxing anything you can. If this solves your problem, try resetting
the limits one by one to find the offending one. If you use bash as your
shell, ulimit is a built-in command. Type "man bash" and look for ulimit in
the resulting man page for the options. Something similar probably holds for
other shells, but I can't tell you exactly (I use bash).

> 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.

Ouch! I believe version 9 of the evaluation/free academic use intel
compilers are still somewhat buggy: I was never able to produce a working
octopus using them, it always segfaulted. Try to find an older version of
the Intel compilers (versions 7 used to work fine, I did not try versions 8)
or using the g95 free compiler, last time I tried it worked. The resulting
executable is rather slow, but it works. Unfortunately, the gfort compiler
is not yet able to compile octopus.

I hope this helps...

Bye
Giacomo

-- 
_________________________________________________________________

Giacomo Mulas <gmulas at ca.astro.it>
_________________________________________________________________

OSSERVATORIO ASTRONOMICO DI CAGLIARI
Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA)

Tel. (OAC): +39 070 71180 248     Fax : +39 070 71180 222
Tel. (UNICA): +39 070 675 4916
_________________________________________________________________

"When the storms are raging around you, stay right where you are"
                          (Freddy Mercury)
_________________________________________________________________

-- 
Il messaggio e' stato analizzato alla ricerca di virus o
contenuti pericolosi da MailScanner, ed e'
risultato non infetto.