Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <19991213222618.22533.qmail@web802.mail.yahoo.com>
Date: Mon, 13 Dec 1999 14:26:18 -0800 (PST)
From: Rick Rankin <rick_rankin AT yahoo DOT com>
Subject: Re: signal error -3, Win32 error 317
To: Chris Faylor <cgf AT cygnus DOT com>
Cc: Cygwin <cygwin AT sourceware DOT cygnus DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Are the messages below related at all? I'm using the 12/01 snapshot and Mumit's
gcc-2.95.2. After approx 2 to 6 hours of use, XEmacs 21.2 beta 23 crashes on me
with these messages in a stackdump file. Once the crash occurs, it *seems* to
occur at shorter intervals.

    0 60009924 [main] xemacs-21.2-b23 1169 sig_send: wait for sig_complete
event failed, sig 6, rc 258, Win32 error 0
 8024 60017948 [sig] xemacs-21.2-b23 1169 sig_send: wait for sig_complete event
failed, sig 11, rc 258, Win32 error 0
 3256 60021204 [main] xemacs-21.2-b23 1169 sig_send: wait for sig_complete
event failed, sig 6, rc 258, Win32 error 0

I asked the XEmacs-NT list about this, and got only one response indicating
that the person is not seeing this problem when building an earlier version of
XEmacs (21.1.8) with the Cygwin 1.0 CD.

It looks to me like a Cygwin problem rather than an XEmacs problem. Is that
true or could it still be an XEmacs problem?

Thanks,

Rick
--
Rick Rankin
rick_rankin AT yahoo DOT com

--- Chris Faylor <cgf AT cygnus DOT com> wrote:
> On Mon, Dec 13, 1999 at 12:36:40PM -0800, Bob McGowan wrote:
> >I am using the cygwin tools to run UNIX developed test scripts in a
> >WinNT environment.  One of the scripts, every once in a while, will
> >generate the following error:
> >
> >1617775739 -1867899777 [main] bash 7805 sig_send: error sending signal
> >-3 to pid 7805, semaphore 0x8C, Win32 error 317
> >
> >The first two numbers and the PID values vary, but the signal number,
> >semaphore value and Win32 error number are consistently the same.
> >
> >The event does not appear to cause any problem with the script itself,
> >since it continues to run.  I am curious if anyone can tell me what is
> >happening here.  Is there a bug that I have uncovered or am I just
> >pushing the limits of the system?
> 
> It's a harmless bug which should be fixed in recent snapshots.
> 
> cgf
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
> 
> 

__________________________________________________
Do You Yahoo!?
Thousands of Stores.  Millions of Products.  All in one place.
Yahoo! Shopping: http://shopping.yahoo.com

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