contour/render crash

Thread View: comp.graphics.explorer

3 messages

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

3 total messages Started by g.j.milne Thu, 03 Sep 1992 13:17

#117

Author: g.j.milne
Date: Thu, 03 Sep 1992 13:17

13 lines
1084 bytes

I've set up a simple network with ReadLat, GenerateColormap, Contour
and Render and used the example data in
/usr/explorer/data/lattice/testVol.lat. After a couple of modifications
to the Contour panel everything seems to hang (ie no more redraws). The
machine appears to lock up, but remote access shows that Render is
hogging the CPU. Eventually, Contour dies (segmentation violation) and
disappears from the Map editor.

Has anyone got any ideas? (I have seen this problem on two machines).
---
S.E.R.C. Daresbury Laboratory, Warrington, WA4 4AD, United Kingdom.
e-mail     : g.j.milne@dl.ac.uk (INTERNET)  g.j.milne@uk.ac.daresbury (JANET)
Opinions expressed are my own, not necessarily those of my employer!

Re: contour/render crash

#120

Author: Roger Crawfis
Date: Thu, 03 Sep 1992 23:06

5 lines
588 bytes

Shoot. I always mess that up.
I meant to post that, not reply. Oh well, sorry about that. I
will post it to the net now.

Roger

Re: contour/render crash

#119

Author: Roger Crawfis
Date: Thu, 03 Sep 1992 23:10

29 lines
1867 bytes

I can not answer your specific question, but I too have noticed
hand-ups, core dumps, obtuce messages, etc. I seems that one
needs to know a lot of system stuff to run Explorer effectively.
Which is to be expected for the power and flexibility it offers.
So here are some observations. Let's have people add their own and
maybe we can start a FAQ.

Check these things when things go haywire:
   df  - check to see that your not running out of Arena or swap space
   tail -40 /usr/adm/SYSLOG  - this keeps a log of system errors

If your getting messages such as "Can not connect to named pipe", or
a slew of others. Go to another window and pwd, ls, df, etc might
give you a message such as too many open files. You need to rebuild
the kernel with better system variables - see /usr/explorer/unsupported/
Installation. Worse yet, anytime you install something?, the operating
system, you need to redo this.

Finally, I have noticed that explorer just won't work when you set
up the arena in a NFS mounted file system. I had it set to my scratch
disk which was fine, until I logged onto our 320/VGX which is cross-
mounted and uses the same ~/.explorerc file. They may actual document
this, but this is a reminder.

Let's see, any others?

Roger Crawfis
Lawrence Livermore National Laboratory
(crawfis@llnl.gov)

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