Re: [Openais] Corosync/openais segfault
05.04.2011 19:34, Steven Dake wrote: On 04/05/2011 09:53 AM, Vladislav Bogdanov wrote: 05.04.2011 19:41, Steven Dake wrote: This could be one of two things. Either a bug in the lock service around reference counting, or a known issue we have resolved with recursion that causes stack corrution. We will release a new version of 1.3 in the next week or so. Does this mean that current trunk is stable? The flatiron-1.3 branch has these problems fixed. The flatiron branch also has these problems fixed. I am waiting for some third party QE to release a z stream in the 1.3 stream. Do you mean commit e6597c7a1cd0230428815edf13e175315a2dbd31 (totemsrp: Remove recv_flush code) in flatiron-1.3? If not, can you point me to a correct commit in that branch? Best, Vladislav ___ Openais mailing list Openais@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/openais
Re: [Openais] Corosync/openais segfault
On 04/07/2011 12:45 PM, Vladislav Bogdanov wrote: 05.04.2011 19:34, Steven Dake wrote: On 04/05/2011 09:53 AM, Vladislav Bogdanov wrote: 05.04.2011 19:41, Steven Dake wrote: This could be one of two things. Either a bug in the lock service around reference counting, or a known issue we have resolved with recursion that causes stack corrution. We will release a new version of 1.3 in the next week or so. Does this mean that current trunk is stable? The flatiron-1.3 branch has these problems fixed. The flatiron branch also has these problems fixed. I am waiting for some third party QE to release a z stream in the 1.3 stream. Do you mean commit e6597c7a1cd0230428815edf13e175315a2dbd31 (totemsrp: Remove recv_flush code) in flatiron-1.3? If not, can you point me to a correct commit in that branch? Best, Vladislav thats the commit regards -steve ___ Openais mailing list Openais@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/openais
Re: [Openais] Corosync/openais segfault
On 04/05/2011 09:53 AM, Vladislav Bogdanov wrote: 05.04.2011 19:41, Steven Dake wrote: This could be one of two things. Either a bug in the lock service around reference counting, or a known issue we have resolved with recursion that causes stack corrution. We will release a new version of 1.3 in the next week or so. Does this mean that current trunk is stable? The flatiron-1.3 branch has these problems fixed. The flatiron branch also has these problems fixed. I am waiting for some third party QE to release a z stream in the 1.3 stream. Regards -steve ___ Openais mailing list Openais@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/openais
