X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 29 Feb 2012 16:01:10 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: BLODA detection code in latest snapshot
Message-ID: <20120229150110.GA20306@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20120227122614 DOT GB31025 AT calimero DOT vinschen DOT de> <4F4E3B6C DOT 1080607 AT cs DOT utoronto DOT ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4F4E3B6C.1080607@cs.utoronto.ca>
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: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 Feb 29 09:51, Ryan Johnson wrote:
> On 27/02/2012 7:26 AM, Corinna Vinschen wrote:
> >Hi folks,
> >
> >
> >I've just uploaded a new snapshot "2012-02-27 12:04:23 UTC".  It
> >contains two code snippets which are supposed to help diagnosing BLODA
> >problems.
> >
> >If you set the environment variable CYGWIN to "detect_bloda" and then
> >start a Cygwin process (bash or so), then Cygwin will detect two types
> >of anomalies:
> >[...]
> Would it be a good idea to update the FAQ's bloda entry with this
> info? Sure, it's probably going to give occasional false positives
> and/or negatives, but it would definitely catch the obvious cases
> and give a quick test for claims of bloda-free systems. You'd almost
> want a new cygcheck -b option that could fork off a process or two
> with detect_bloda active and capture any output that results.

Of course I will document this at one point.  So far I just didn't.
I doubt that the cygcheck -b would be useful, though.  Just call

  $ export CYGWIN=detect_bloda some_executable

and you get what you want.


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