On Aug 30, 2012, at 17:15 , Ralph Castain wrote:
>
> On Aug 30, 2012, at 8:10 AM, George Bosilca wrote:
>
>> A strange race condition happening for undisclosed reasons, and only fixable
>> by replication is jeopardizing our reference count system.
On Aug 30, 2012, at 8:10 AM, George Bosilca wrote:
> A strange race condition happening for undisclosed reasons, and only fixable
> by replication is jeopardizing our reference count system. That sounds
> definitively almost scary (!)
>
> I think that the proposed
A strange race condition happening for undisclosed reasons, and only fixable by
replication is jeopardizing our reference count system. That sounds
definitively almost scary (!)
I think that the proposed solution is just a band-aid. It somehow fixes this
particular instance of the issue but
Yes, we know - been fixed.
On Aug 30, 2012, at 7:50 AM, Eugene Loh wrote:
> Trunk broken? Last night, Oracle's MTT trunk runs all came up empty handed.
> E.g.,
>
> *** Process received signal ***
> Signal: Segmentation fault (11)
> Signal code: Address not mapped (1)
Trunk broken? Last night, Oracle's MTT trunk runs all came up empty
handed. E.g.,
*** Process received signal ***
Signal: Segmentation fault (11)
Signal code: Address not mapped (1)
Failing at address: (nil)
[ 0] [0xe600]
[ 1] /lib/libc.so.6(strlen+0x33) [0x3fa0a3]
[ 2]