Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.220.175 as permitted sender)
	client-ip=209.85.220.175; envelope-from=mh.in.england@gmail.com;
	helo=mail-vx0-f175.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <1312995554.17416.22.camel@BMThinkPad.lan.bluematt.me>
References: <CABsx9T2pTg8YG_Q09cnAvsrxquLO-6cWr1tb=fdWtLPBEyJzng@mail.gmail.com>
	<1312995554.17416.22.camel@BMThinkPad.lan.bluematt.me>
Date: Thu, 11 Aug 2011 13:56:34 +0200
Message-ID: <CANEZrP35RKSGmAOiqp=fm2z97u+njGsOaPC0ttWXYfki6chR=g@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Matt Corallo <bitcoin-list@bluematt.me>
Content-Type: text/plain; charset=UTF-8
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Roadmap/schedules
Precedence: list

> they don't look good (I show about 3x as many 0.3.23 nodes listening as
> 0.3.24

*cough* Upgrade alerts.

> Very much needed, didn't TD say something about a friend who wanted to
> do research in this area?

I don't know if he'll actually do anything. Best assume this
"position" is still open.

>> 2. We've got a chronic problem with new code causing CRITICAL_SECTION
>> deadlocks

I've seen locks that track ordering relative to other locks and assert
when they are locked out of order.

Though it's not inversion related, running ThreadSanitizer might help
find other thread safety issues:

http://code.google.com/p/data-race-test/wiki/ThreadSanitizer