Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<002a01c044da$1dfb6d70$2a02a8c0@tff.ca>
From:	"Boris Gjenero" <bgjenero AT sympatico DOT ca>
To:	<cygwin AT sourceware DOT cygnus DOT com>
Subject:	Couldn't send signal 14: part 2
Date:	Thu, 2 Nov 2000 09:35:15 -0500
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400

I reallize that my previous post about this may not have been too useful
because the problem was with a large, newly-ported application and I was
running with a modified Cygwin.   Now I performed an experiment that should
clear up some things.

I compiled cou_svc from the Windows port of ONC RPC
(ftp://ftp.fh-wiesbaden.de/pub/UNIX/comm/rpc/srpc111.zip) on cygwin using
libnsl from flick-2.1 (see http://www.cs.utah.edu/flux/flick/).  cou_svc is
a simple demonstration/test RPC server program.  I just modified it so that
it gets SIGALRM (yes, signal 14) every second.  I ran the program with a
totally normal, non-modified copy of Cygwin 1.1.4.

After a few minutes cou_svc died with:
C:\cygwin\home\administrator\sig14\cou\cou_svc.exe: *** couldn't send signal
14

I think this narrows things down a bit.

BTW.  Yeah, my last subject line was wrong.  It is signal 14 and not 13.



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -