X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 17 Aug 2012 11:39:20 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: False BLODA warning concerning cygusb? Message-ID: <20120817093920.GC26407@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <502DA4D4 DOT 4040809 AT aa DOT net DOT uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <502DA4D4.4040809@aa.net.uk> User-Agent: Mutt/1.5.21 (2010-09-15) 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 17 02:56, Cliff Hones wrote: > I am seeing the following when invoking a utility which uses libusb to > drive a USB JTAG interface dongle: > > Potential BLODA detected! Thread function called outside of Cygwin DLL: > C:\cygwin1.7\bin\cygusb-1.0.dll > > I've had CYGWIN=detect_bloda set for some time (months), and the > utility (developed locally) has never triggered this before, so > I think a recent Cygwin update has triggered this. (Note cygusb > has not changed since last year.) > > I'll happily submit full cygcheck details if that would prove useful - > the relevant details (AFAICS) are: I have no problems with occassional false postives. The detect_bloda option is meant for diagnostic purposes only. It's not meant to used all the time. It slows down *every* thread start up! Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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