X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 19 Aug 2008 10:39:32 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Bug in cygcheck (1.7) Message-ID: <20080819083932.GN21040@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <48A8188E DOT 4030203 AT elite-systems DOT org> <20080817165425 DOT GA3708 AT ednor DOT casa DOT cgf DOT cx> <48A85BA5 DOT 20501 AT cwilson DOT fastmail DOT fm> <48A8E552 DOT 3070803 AT cwilson DOT fastmail DOT fm> <20080818032220 DOT GA28914 AT ednor DOT casa DOT cgf DOT cx> <48A8F8A7 DOT 8080805 AT cwilson DOT fastmail DOT fm> <20080818133930 DOT GK21040 AT calimero DOT vinschen DOT de> <20080818141142 DOT GA32164 AT ednor DOT casa DOT cgf DOT cx> <20080818143410 DOT GM21040 AT calimero DOT vinschen DOT de> <20080818164109 DOT GA2384 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080818164109.GA2384@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.16 (2007-06-09) 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 On Aug 18 12:41, Christopher Faylor wrote: > On Mon, Aug 18, 2008 at 04:34:10PM +0200, Corinna Vinschen wrote: > >On Aug 18 10:11, Christopher Faylor wrote: > >> On Mon, Aug 18, 2008 at 03:39:30PM +0200, Corinna Vinschen wrote: > >> >So it's the FreeLibrary call which triggers the problem. What I don't > >> >understand so far is, why it does. > >> > >> Does this have any effect? > > > >Unfortunately not, it doesn't even change the frequency in which it > >occurs. I can so far only fix the problem by avoiding to call > >FreeLibrary. Disabling the call to shared_destroy from dll_entry > >doesn't help either. > > Did you try commenting out the stuff in DLL_THREAD_DETACH too? Looking at > the code, it *shouldn't* be an issue but if it was actually getting called > there would be all sorts of repercussions. Yes, I did. It didn't change anything, as you suspected. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/