Bill Storma (BILLS++at++p3.enzian.com)
Fri, 3 Jan 1997 11:01:53 EST
I am having a problem with a child process dying in a draw process,
due to a segmentation violation. Apparently the performer code
captures this event and issues a note of the event, then dies. This
implies that the child is notifing the parent of the event. However,
the parent performer app does not issue any type of warning to the
user code that the application is terminating.
Does performer provide some type of mechanism to let the user code
know of an impending termination of the program, or do I have to
write my own signal handlers in the parent and child to do this ?
Currently, I have trapped SIGSEGV in the child process to determine
where the program is dying. But I do not get any SIGCHLD signal in
the parent (I assume Performer overrode my signal handler). My only
course of action currently is to send a signal other than SIGCHLD from
the child to the parent to notify the parent that the child is dying.
That way, the parent can exit via a different route than a normal
termination. Is there a better way to do this ?
Thanks.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Bill Storma Phone: 407-282-1884
Enzian Technology FAX: 407-282-3013
Orlando, Fl. 32817 e-mail: bills++at++p3.enzian.com
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:54:16 PDT