Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Wed, 5 Jul 2000 19:46:51 -0400 From: Chris Faylor To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: _impure_ptr uninitialized in DLLs? Message-ID: <20000705194651.A16474@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin-developers AT sourceware DOT cygnus DOT com References: <779F20BCCE5AD31186A50008C75D9979171740 AT silldn_mail1 DOT sanwaint DOT com> <20000705140542 DOT A7151 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000705140542.A7151@cygnus.com>; from cgf@cygnus.com on Wed, Jul 05, 2000 at 02:05:42PM -0400 On Wed, Jul 05, 2000 at 02:05:42PM -0400, Chris Faylor wrote: >On Wed, Jul 05, 2000 at 12:50:29PM +0100, Fifer, Eric wrote: >>Starting with the Jul-01 snapshot, something changed with the handling >>of _impure_ptr so that within a newly compiled DLL its value is NULL. >>Previously compiled DLLs continue to work. Presumably this is related >>to the restructuring of user_data. >> >>I'll try to hunt down the problem, but thought I should report it in >>the meantime. > >I see the problem. I don't know how to solve it yet but I'm >working on it. > >I'm glad that you found this. If we'd released a version of the Cygwin >DLL with this problem there would have been hell-to-pay. I've checked in a fix for this. It was pretty tricky. Let's see if I actually got it right. cgf