Re: variable content lost

Listad <listad@xxxxxxxxx> wrote:

This might be completely unrelated, but I had trouble earlier with the
values of these arrays. Whenever I tried 'print *, fib%r(m,:)' in my
code the first element of the array changed to sth like 2.932434E-310.
In addition to that I either got 'segmentation fault' or a 'malloc-
exception'. After I changed the print statements to write statements
with explicit format the problem dissapeared ...

That value looks very much like one from type mismatch - interpreting
bits as double precision when the bits were generated as some other
type(s). This could be a symptom of something like a type mismatch in a
procdure call. Or it could be a symptom of exceeding array bounds or
referencing invalid pointers.

Your comment about changing the print to write statements supports the
theory of exceeding array bounds or referencing invalid pointers. You
are probably stepping on memory that "belongs" to something else. WHat
the "something else" is can depend on all kinds of apparently unrelated
things. This has very much the symptoms of that kind of bug.

--
Richard Maine | Good judgement comes from experience;
email: last name at domain . net | experience comes from bad judgement.
domain: summertriangle | -- Mark Twain
.