X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_73
X-Spam-Check-By:	sourceware.org
Message-ID:	<4A850558.1050109@lysator.liu.se>
Date:	Fri, 14 Aug 2009 08:34:00 +0200
From:	Peter Rosin <peda AT lysator DOT liu DOT se>
User-Agent:	Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-58
References:	<announce DOT 20090813160632 DOT GM13438 AT calimero DOT vinschen DOT de>
In-Reply-To:	<announce.20090813160632.GM13438@calimero.vinschen.de>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

> Bugfixes:
> =========
> 
> - Fix and workaround a bug in the implementation of the C++ memory
>   allocation support introduced in 1.7.0-49.  A structure pointer got
>   accidentally manipulated when DLLs got loaded at runtime via dlopen.
>   When dlclose'ing the same DLL, the pointer content pointed into the
>   memory of the just unloaded DLL, with probably unexpected results.
>   This fixes the problem reported in
>   http://cygwin.com/ml/cygwin/2009-08/msg00352.html

I can confirm that it also fixes my (not so simple) real world case.
Thanks to all involved for the speedy resolution!

Cheers,
Peter

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -