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: <001f01c04440$13ef75f0$2a02a8c0@tff.ca>
From: "Boris Gjenero" <bgjenero AT sympatico DOT ca>
To: <cygwin AT sourceware DOT cygnus DOT com>
Subject: couldn't send signal 13
Date: Wed, 1 Nov 2000 15:12:36 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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

My NFS server sometimes dies with:
C:\nfscygwin\bin\rpc.nfsd.exe: *** couldn't send signal 14

According to /usr/include/sys/signal.h, signal 14 is SIGALRM.  This signal
is used by the NFS server for flusing a cache, and it is called normally
every 5 seconds or at most every 2 seconds in certain conditions.  So it
seems it must work most of the time.  It's just that once in a while the
signal can't be sent for some reason.

I'm wondering is the bug in the NFS server or in Cygwin 1.1.4.  The Cygwin
I'm using has some modifications in the file attribute handling parts, so I
guess that could be to blame too.

I've tried to understand what is going on.  It seems that the only place
that could be printing that message is interrupt_on_return in
winsup/cygwin/exceptions.cc.   Apparently, the function searches through the
last 32 stack frames looking for an interruptible function, and if it finds
one it makes the signal happen when a return into that function happens.  If
this fails then either the stack is corrupted or the last 32 stack frames
are all for non-interruptible functions or perhaps more likely one
non-interruptible recursive function.  Have I got this right?  It's kind of
twisted.




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