Xref: utzoo comp.sys.next:7654 comp.os.mach:524
Path: utzoo!attcan!uunet!jarthur!usc!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!news
From: olson@sax.cs.uiuc.edu (Robert Olson)
Newsgroups: comp.sys.next,comp.os.mach
Subject: Threads and signals
Message-ID: <1990Sep16.202349.20124@ux1.cso.uiuc.edu>
Date: 16 Sep 90 20:23:49 GMT
Sender: news@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 17

I'm trying to take an existing application and create a thread to
handle some communication with another application via a port (I'm
actually using the NextStep speaker/listener). The problem is that the
application is using SIGIO to notify itself of keypresses. When I add
another thread for communication, the communication thread is the one
that actually gets the signal, some of the time (when I type quickly at
the application), hanging the application. Is there any way I can keep
the thread from getting the signal? I tried doing a sigblock, but then
the application didn't get the signals either.

--bob

--
Bob Olson			University of Illinois at Urbana/Champaign
Internet: rolson@uiuc.edu	UUCP:  {uunet|convex|pur-ee}!uiucdcs!olson
NeXT mail: olson@fazer.champaign.il.us
"You can't win a game of chess with an action figure!" AMA #522687 DoD #28