From: Mike Hearn <mike@plan99•net>
To: Matt Corallo <bitcoin-list@bluematt•me>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Roadmap/schedules
Date: Thu, 11 Aug 2011 13:56:34 +0200 [thread overview]
Message-ID: <CANEZrP35RKSGmAOiqp=fm2z97u+njGsOaPC0ttWXYfki6chR=g@mail.gmail.com> (raw)
In-Reply-To: <1312995554.17416.22.camel@BMThinkPad.lan.bluematt.me>
> 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
next prev parent reply other threads:[~2011-08-11 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 16:29 Gavin Andresen
2011-08-10 16:59 ` Matt Corallo
2011-08-10 18:57 ` Pieter Wuille
2011-08-11 11:56 ` Mike Hearn [this message]
2011-08-11 17:49 ` bgroff
2011-08-10 20:41 ` Jeff Garzik
2011-08-11 8:48 ` Matt Corallo
2011-08-11 18:20 ` Rick Wesson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANEZrP35RKSGmAOiqp=fm2z97u+njGsOaPC0ttWXYfki6chR=g@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-list@bluematt$(echo .)me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox