Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!ncr-sd!conan!garyb
From: garyb@conan.SanDiego.NCR.COM (Gary Boggs)
Newsgroups: comp.sys.isis
Subject: ISIS and signal handling on Unix V.3
Message-ID: <2731@ncr-sd.SanDiego.NCR.COM>
Date: 29 May 90 22:40:45 GMT
Sender: news@ncr-sd.SanDiego.NCR.COM
Reply-To: gary.boggs@SanDiego.NCR.COM (Gary Boggs)
Distribution: usa
Organization: NCR Corporation, Rancho Bernardo
Lines: 20

[][][]

Hello,

I'm attempting to port ISIS (V1.3) to an NCR Tower which runs AT&T Unix
V.3 plus some berkeleyisms. My problem is that my kernel is getting confused 
by the ISIS threads package. When a signal (e.g. SIGCLD) comes in, the 
sendsig() routine that is supposed to build a stack frame for the signal 
catching function becomes baffled because the stack pointer is not in the 
normal stack region. It then gives up and aborts the process by calling exit().

Has anybody out there experienced this and found a solution? Any ideas?

Please respond by e-mail.

Thanks,

Gary Boggs
NCR Corp. E&M San Diego
gary.boggs@sandiego.ncr.com