Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Wed, 31 Dec 2003 17:03:44 -0500
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 1.5.6-pre: Occasional bad memory accesses within cygwin1.dll
Message-ID: <20031231220343.GA5793@redhat.com>
Mail-Followup-To: cygwin@cygwin.com
References: <3.0.5.32.20031231100244.0082ad10@verizon.net> <20031231163808.GA3595@redhat.com> <Pine.GSO.4.58.0312311216110.23399@eos>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.58.0312311216110.23399@eos>
User-Agent: Mutt/1.4.1i
X-IsSubscribed: yes
Reply-To: cygwin@cygwin.com

On Wed, Dec 31, 2003 at 12:20:12PM -0600, Brian Ford wrote:
>On Wed, 31 Dec 2003, Christopher Faylor wrote:
>
>> On Wed, Dec 31, 2003 at 10:02:44AM -0500, Pierre A. Humblet wrote:
>> >Christopher Faylor wrote:
>> >>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?
>>
>Yep.  That change just wasn't enough.  Here's the next spot.

Is this with the snapshot or with something that you built yourself?
It's hard to comprehend why I would be seeing something so radically
different since this problem is occuring before there is even another
thread around to screw up this memory.

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/

