Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Wed, 31 Dec 2003 11:38:08 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.6-pre: Occasional bad memory accesses within cygwin1.dll
Message-ID: <20031231163808.GA3595@redhat.com>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3 DOT 0 DOT 5 DOT 32 DOT 20031231100244 DOT 0082ad10 AT verizon DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3.0.5.32.20031231100244.0082ad10@verizon.net>
User-Agent: Mutt/1.4.1i
Reply-To: cygwin AT cygwin DOT com

On Wed, Dec 31, 2003 at 10:02:44AM -0500, Pierre A. Humblet wrote:
>Christopher Faylor wrote:
>>>Oh.  This is probably with current CVS, which is broken.  Known problem.
>>>It's why I haven't generated a snapshot yet.
>
>>This should be fixed now.  I'm uploading a snapshot.
>
>CYGWIN_ME-4.90 hpn5170x 1.5.6s(0.108/3/2) 20031231 01:31:40 i686 unknown
>unknown Cygwin
>
>Now virtually every cygwin program (/bin/true, ls, uname,...) almost
>always ends with the popup about causing an error in Cygwin1.dll. 

Did you look at the changes I made?  It's difficult to believe that minor
changes to cygwin.din would cause a popup on every access, although I can
believe that the stuff in CVS previously would work that way.  If anything,
I'd expect that there would be no change rather than actual worsening.

Are you sure you're up to date?

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/