Xref: utzoo comp.os.vms:4334 comp.unix.wizards:6286
Path: utzoo!mnetor!uunet!kddlab!ccut!wadalab!rikitake
From: rikitake@wadalab.t.u-tokyo.JUNET (rikitake)
Newsgroups: comp.os.vms,comp.unix.wizards
Subject: Re: c signals with VMS
Message-ID: <161@wadalab.t.u-tokyo.JUNET>
Date: 22 Jan 88 02:05:46 GMT
References: <127@insyte.uucp>
Organization: Wada Lab., Univ. Tokyo
Lines: 31
Keywords: c signals fork exec subprocesses VMS LIB$SPAWN
Summary: Check LIB$SIGNAL


>Does anyone know exactly how the c signals correspound and interact 
>with the VMS system ones?  Can anyone explain this behavior or even 
>better, tell me how to fix it?

Several thing I know about VAX C signals:

* VAX C signals are handled by C$SIGNAL run time module, and
  actually handled by LIB$SIGNAL library routine.
* VAX C signals acts like those in UNIX System V. Every time
  a signal accepted, the vectore of the signal will be reset
  to SIG_DFL. In the signal handling funtion. you have to
  rewrite the vector, if you are using other than SIG_DFL.

And about VMS signals:

* There's a LIB routine called LIB$DISABLE_CTRL and
  LIB$ENABLE_CTRL. This directly handle CTRL/T and
  CTRL/Y masks.

I don't know if the signal environment inherits...

-- Kenji
(Reference: VAX C 1.0 Japanese manual, DEC Japan)
(Please do NOT reply via JUNET: please send to KENJI@DCTWCS.DAS.NET.)

-- 
Kenji Rikitake / Studying instrumentation physics in Univ. of. Tokyo.
KENJI@DCTWCS.DAS.NET or ...!Sun!DCTWCS.DAS.NET!Kenji, for people overseas.
#102, 4-19-11, Sakurajousui, Setegaya-ku, Tokyo 156 JAPAN phone +81 3 306 0330
Also TWICS BeeLINE operation staff. Office +81 3 351 5977