Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Fri, 9 Mar 2001 22:57:30 -0500 From: Christopher Faylor To: cygwin@cygwin.com Cc: David Highley Subject: Re: Stack Dump Problem Message-ID: <20010309225730.B3200@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com, David Highley References: <200103091619.f29GJt710563@hemlock.highley-recommended.com> <20010309222859.A1355@dothill.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010309222859.A1355@dothill.com>; from Jason.Tishler@dothill.com on Fri, Mar 09, 2001 at 10:28:59PM -0500 On Fri, Mar 09, 2001 at 10:28:59PM -0500, Jason Tishler wrote: >David, > >On Fri, Mar 09, 2001 at 08:19:55AM -0800, David Highley wrote: >> Since upgrading my cygwin environment I get a stack dump when trying to >> run aspell from within vim. I have included the setup log file fragment >> of cygwin subsystems updated and the stack dump file. > >I found that replacing the cygwin1.dll with a post 1.1.8-2 version solved >my aspell stack dump problem (and others). However, this is probably >not the best workaround since Chris has already indicated that the problem >appears to be with aspell itself. Hmm. Did I miss an explanation for this? The stack dump shows multiple levels of calls of a user program so I ass*u*me*d that this was not a Cygwin problem. Has this already been discussed? Do we know why aspell works better with snapshots? I have no problem with a workaround that involves moving forward and testing the snapshots. Eventually one of those snapshots will be Cygwin 1.3.0. It would be nice to see people trying them out. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple