Re: matmul trouble

Wade Ward <invalid@xxxxxxxxxxxx> wrote:

I thought matmul was the culprit, but it's the write statement.

Well. That's where you see the error. That doesn't necessarily mean that
is actually where the problem is. If matmul was corrupting memory
somehow, then the symptoms could well show up later, as in the
subsequent write statement.

That's not to say that I have any concrete evidence that it is the
matmul. Just pointing out that you might be looking too narrowly.

Afraid I don't have any good ideas, anyway not ones I could plausibly
work remotely. If I were sitting in front of the machine with code that
demonstrated the problem, I'd probably fiddle around with lots of things
for clues. But I can't do that remotely. Not even worth trying at that
level. I'm talking about the kind of fiddling where I'd probably go
through several dozen fruitless things before getting much of a hint.
Even if you have the patience for that kind of thing remotely, I don't.
(And I'd loose track of my line of thought between turnarounds anyway).

I'm sort of inclined to ask for details about compiler, OS, and
environmental issues (run from command line, a GUI, whatever...), but I
can't see how that is actually going to help my diagnosis, as I can't
imagine any answer that would give me better ideas. Maybe someone else
would have an idea, though.

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