X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_73,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4A850558.1050109@lysator.liu.se> References: <4A850558 DOT 1050109 AT lysator DOT liu DOT se> Date: Fri, 14 Aug 2009 12:18:33 +0200 Message-ID: <6910a60908140318u6038677ctbf930580bc49540d@mail.gmail.com> Subject: Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-58 From: Reini Urban To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 2009/8/14 Peter Rosin : >> Bugfixes: >> =3D=3D=3D=3D=3D=3D=3D=3D=3D >> - Fix and workaround a bug in the implementation of the C++ memory >> =A0allocation support introduced in 1.7.0-49. =A0A structure pointer got >> =A0accidentally manipulated when DLLs got loaded at runtime via dlopen. >> =A0When dlclose'ing the same DLL, the pointer content pointed into the >> =A0memory of the just unloaded DLL, with probably unexpected results. >> =A0This fixes the problem reported in >> =A0http://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! It also fixed my problem reported at http://cygwin.com/ml/cygwin/2009-08/msg00114.html so it was indeed related. Thanks! --=20 Reini Urban http://phpwiki.org/ http://murbreak.at/ -- 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