🚀 go-pugleaf

In article <dieter.715519092@sun-3>, dieter@sun-3.cs.uct.ac.za (Dieter Polzin) writes:
|> I have recently started using explorer. I wrote a module to read data from a
|> file into a 2D uniform lattice. This lattice and another of the same size
|> are fed into DisplaceLat which is then fed into LatToGeom. On the first run
|> everything works fine. But if I then go change the scale in DisplaceLat or
|> change something in LatToGeom, the latter usually core dumps. I must say that
|> I am using a big lattice (dims[0] = dims[1] = 300) but the strange thing is
|> that it used to work a few weeks back. We have, however, installed IRIX 4.0.2
|> in the meantime, could that be the problem?
|> I am aware that the problem could be with my module, but after its fired the
|> first time I usually don't use it again. If I fire LatToGeom more than once
|> though, it is likely to core dump.

All manner of weird and wonderful things are possible with shared memory.

I tried the same thing with GenLat as a source, and didn't have any
problem.  Set up GenLat to the primitive type and numDataVars that
simulate your module, and if it works for you, then it must be your
module.

-- 

Robert Skinner
robert@sgi.com

	"The sendmail configuration file is one of those files that
	looks like someone beat their head on the keyboard. After
	working with it... I can see why!"

				-- Harry Skelton (harry@usrgrp)