blob: 7758f6096d9cafff10f5486b8b2db82c07ec7b42 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1QrTsL-00048k-TQ
for bitcoin-development@lists.sourceforge.net;
Thu, 11 Aug 2011 11:56:37 +0000
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;
Received: from mail-vx0-f175.google.com ([209.85.220.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QrTsJ-0007eh-44
for bitcoin-development@lists.sourceforge.net;
Thu, 11 Aug 2011 11:56:35 +0000
Received: by mail-vx0-f175.google.com with SMTP id 14so2301636vxj.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 11 Aug 2011 04:56:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.90.48 with SMTP id bt16mr10164459vdb.197.1313063794957;
Thu, 11 Aug 2011 04:56:34 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.52.164.165 with HTTP; Thu, 11 Aug 2011 04:56:34 -0700 (PDT)
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
X-Google-Sender-Auth: YLx0KiGooTxZGFYJ3HwmcIGav5s
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
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.9 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QrTsJ-0007eh-44
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Roadmap/schedules
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 11:56:38 -0000
> 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
|
