[684] in Pthreads mailing list archive
Possible bug (workaround) w/signal.c for SunOS 4.1.4
daemon@ATHENA.MIT.EDU (RHS Linux User)
Wed Jul 16 17:39:13 1997
Date: Wed, 16 Jul 1997 23:40:27 +0300
From: RHS Linux User <monty@monty.pp.sci.fi>
To: beckwith@whinny.tdh.qntm.com (Bob Beckwith)
Cc: pthreads@MIT.EDU
In-Reply-To: <9707152138.AA12878@whinny>
Reply-To: monty@analytikerna.se
>>>>> "Bob" == Bob Beckwith <beckwith@whinny.tdh.qntm.com> writes:
<cut>
Bob> When attempting to initialize signal handlers, the following call to signal()
Bob> on line 594 returned `1' (not 0 or -1) when attempting to set up a signal
Bob> handler for SIGVTALRM:
Bob> if (signal(signum_to_initialize[i], sig_handler_real))
Bob> PANIC();
There is two problems with this code.
1) signal() is forbidden when using threads, you should use
pthread_signal() instead.
2) mit-threads uses SIGVTALRM internally and you can't use this when
using mit-threads. The same is probably tru for all user level thread
implementations.
Monty
