LatToGeom core dumps

Thread View: comp.graphics.explorer

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Dieter Polzin Thu, 03 Sep 1992 11:18

#116

Author: Dieter Polzin
Date: Thu, 03 Sep 1992 11:18

15 lines
1263 bytes

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.

If anybody has any ideas, I would appreciate hearing them.
Thanks
Dieter

Re: LatToGeom core dumps

#122

Author: Robert Skinner
Date: Fri, 04 Sep 1992 00:29

30 lines
1993 bytes

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)

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads