🚀 go-pugleaf

In article <up5dq14@zuni.esd.sgi.com> olson@anchor.esd.sgi.com (Dave Olson) writes:

   From: olson@anchor.esd.sgi.com (Dave Olson)
   Date: 12 Jan 93 06:28:04 GMT


   In <MBR.93Jan11184839@ponape.bellcore.com> mbr@bellcore.com (Mark Rosenstein) writes:
   | The error on the console is:
   | 
   | WARNING: Process [art-devo.r4000] pid 1227 killed due to bad page read (errno:134)

   This one is easy.  Has nothing to do with memory or swap space.
   errno 134 is: Stale NFS file handle.  You are almost certainly running
   the program over NFS, and the server has re-exported the filesystem 
   differently.  Talk to the system admin of the server.
   I also seem to recall that you can get ESTALE if the file was unlinked
   on the server (which might happen if somebody was remaking the program,
   depending on the makefile).
Foo! You're right. I got overexcited, when I saw the console message, and
thought this was my problem, but these were just old messages. As you suspected
I was running over NFS and remaking the program, but I understood that. My
program really does just die (with no message in the console window) with
the message terminated in cvd.

   | Is there a reasonable way using cvd to stop the process before it
   | terminates and figure out, how I might be managing to do this (like a
   | stack trace)? [My suspicion is that I am doing a Motif no-no, but I 
   | can't really begin to figure it out unless I have some clue as to where
   | I am running into this problem

   No, cvd can't trap this (although it can catch the exit or the signal).

Ok. I was overloading the word trap. My real question was how to catch
this signal in cvd (so I could try and figure out why I was getting
terminated). I set the SIGKILL button in the cvd signal panel, and it
does not seem to catch the termination. I conducted the following simple
experiment to make sure I wasn't totally confused: I ran xclock. I
attached to it with cvd. I set every signal to be caught (including
SIGKILL) in the signal panel. I did kill -INT xxx and cvd caught it. I
did kill -9 xxx, and cvd didn't catch it, and said terminated, just
like my program. [Irix 4.0.5F, 07/15/92 CASEVision Environment,
Version 1.0, 07/15/92 WorkShop CASE products, Version 1.1]. So my question,
I think, still stands.

Finally, is there a man page that tells all the reasons a process can
be terminated?

   I'd be astounded if this was caused by a programming error on your
   part.
Sorry to have misled you.

Mark.
=-=-=-=-=-=
Unless you start somewhere, you'll go nowhere. 
               --Marvin Minsky.