X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18oMDD61S9PsteoUf4i3Sx3 Date: Fri, 17 Aug 2012 10:37:25 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: False BLODA warning concerning cygusb? Message-ID: <20120817143725.GD20284@ednor.casa.cgf.cx> 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> <20120817093920 DOT GC26407 AT calimero DOT vinschen DOT de> <502E212E DOT 10008 AT hones DOT org DOT uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <502E212E.10008@hones.org.uk> User-Agent: Mutt/1.5.20 (2009-06-14) 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 Fri, Aug 17, 2012 at 11:47:10AM +0100, Cliff Hones wrote: >On 17/08/2012 10:39, Corinna Vinschen wrote: > >> 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! > >Thanks. I was only reporting it as I thought I remembered a request >for false positives to be reported. I think that's why I turned the >detect_bloda option on in the first place. I must admit I was also >slightly curious - what is an open-source library (libusb) built >under Cygwin doing that makes it look like BLODA? [Of course I >could spend time looking at the source to find out, but time is >in short supply, so I guess I'll just have to stay curious.] Likely it's not starting threads using posix calls (pthread_create) but using Windows ones (CreateThread). That would imply that libusb assumes that a Cygwin compilation means "build for Windows" rather than "built for Linux". Given that it is trying to access usb functionality, maybe that makes sense and it might be a permanent false positive. cgf -- 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