Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Tue, 5 Apr 2005 00:34:54 -0400
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: XEmacs+aspell failed on cygwin 1.5.14-1
Message-ID:	<20050405043454.GF15452@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
References:	<000001c53989$d6b16560$aa1f7180 AT skk DOT che DOT rpi DOT edu>
Mime-Version:	1.0
In-Reply-To:	<000001c53989$d6b16560$aa1f7180@skk.che.rpi.edu>
User-Agent:	Mutt/1.5.8i

On Mon, Apr 04, 2005 at 10:47:37PM -0400, TX wrote:
>Sorry, I forgot to include the error message in my previous post:
>
>Aspell.exe - Application Error
>
>The instruction at "0x6109f478" referenced memory at "0x00000010".
>The memory could not be "read".

The 2005-04-05 snapshot may fix this problem.  It is being generated now.

I say "may fix" because I could not duplicate the problem but I could
convince myself that there were a couple of potential problems that were
caused by a change to the "muto" initialization in cygwin that I introduced
in 1.5.14.  While tracing through the code I actually came across at least
one case where the new code prevented a handle leak, though, so it wasn't
all bad.

So, please try a snapshot: http://cygwin.com/snapshots/ as soon as a
2005-04-05 snapshot shows up.  Any snapshot newer than that date will be
ok, too.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -