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
Date:	Mon, 13 Dec 1999 19:15:20 -0500
From:	Chris Faylor <cgf AT cygnus DOT com>
To:	Rick Rankin <rick_rankin AT yahoo DOT com>
Cc:	Cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Re: signal error -3, Win32 error 317
Message-ID:	<19991213191520.A25661@cygnus.com>
Mail-Followup-To:	Rick Rankin <rick_rankin AT yahoo DOT com>,
	Cygwin <cygwin AT sourceware DOT cygnus DOT com>
References:	<19991213222618 DOT 22533 DOT qmail AT web802 DOT mail DOT yahoo DOT com>
Mime-Version:	1.0
X-Mailer:	Mutt 1.0i
In-Reply-To:	<19991213222618.22533.qmail@web802.mail.yahoo.com>; from rick_rankin@yahoo.com on Mon, Dec 13, 1999 at 02:26:18PM -0800

On Mon, Dec 13, 1999 at 02:26:18PM -0800, Rick Rankin wrote:
>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

They're not the same thing.  A signal 6 is a SIGABRT and a signal 11 is a
SIGSEGV.

>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?

Inability to send the signal is a cygwin problem.  The signal itself is likely to be
an Xemacs problem.

Note that when I said that this may be fixed in "recent" snapshots I
meant very recent.

cgf

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

- Raw text -