This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 1.5.6-pre: Occasional bad memory accesses within cygwin1.dll

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.


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]