Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Wed, 18 Aug 1999 23:57:05 -0400 To: Jim & Jenn Dumser Cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Description of the new 'ntsec' feature Message-ID: <19990818235705.A9980@cygnus.com> Mail-Followup-To: Jim & Jenn Dumser , cygwin AT sourceware DOT cygnus DOT com References: <37B9E07E DOT 2003DE41 AT vinschen DOT de> <37BA8FA9 DOT 4202522A AT bigfoot DOT com> <19990818185638 DOT B3086 AT cygnus DOT com> <37BB6A7E DOT 4348C5E5 AT bigfoot DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <37BB6A7E.4348C5E5@bigfoot.com>; from Jim & Jenn Dumser on Wed, Aug 18, 1999 at 09:22:54PM -0500 On Wed, Aug 18, 1999 at 09:22:54PM -0500, Jim & Jenn Dumser wrote: >After checking into it a little more, the vim.exe that I was using was >fairly old (it was using cygwinb19.dll); but the core dumps happened >with current executables as well (e.g., less.exe from the b20.1 >distribution). You're saying that a vim that was using cygwinb19.dll was core dumping due to the use of a 19990815 DLL snapshot? I don't understand that at all. However, in general, it's not a good idea to mix B1x binaries with B20+ . If we've done our job right this won't be an issue from now on. >Currently, I have CYGWIN=tty binmode ntea ntsec. If you have any other >ideas what might be causing the core dumps, let me know. The strace would help. Also, the "stacdump" output might provide a clue. -chris -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com