[Date Prev][Date Next]
Re: (ITS#7144) reproducible segfault on slave/consumer during sync-replication
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#7144) reproducible segfault on slave/consumer during sync-replication
- From: firstname.lastname@example.org
- Date: Wed, 1 Feb 2012 22:48:17 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
--On Wednesday, February 01, 2012 10:27 PM +0000 email@example.com wrote:
> Um 01:00 Uhr am 01.02.12 schrieb Howard Chu:
>> Sven Hartge wrote:
>>> On 02/01/12 05:56, Howard Chu wrote:
>>>> firstname.lastname@example.org wrote:
>>> > > I get a very good backtrace, but since this backtrace contains
>>> > > internal information I am a bit hesitant to attach this backtrace
>>> > > to a public bug-report.
>>> > The backtrace you sent shows the crash at a line of code which was
>>> > already patched in RE24 due to ITS#7132. I believe this bug is already
>>> > fixed.
>>> This is good news. Do you have any commit ID so I can try to backport
>>> this fix to the version currently in Debian Squeeze?
>> commit 42faa8393e6cd41a837b526777110b892541773a
> This simple patch applies flawless on 2.4.23 but still segfaults. Will
> try on top of 2.4.28 tomorrow, backtraces will follow then, after I
> verified my findings.
> (Reason for trying this on top of 2.4.23 is because this is the version
> in Debian Squeeze and I want to provide the DDs with a fix for Squeeze.
> I fully understand that is not supported by OpenLDAP.)
Could you *please* try the RE24 checkout from GIT rather than 2.4.28?
Thanks. That is substantially more useful than patching 2.4.28.
You can check out an tarball of current RE24 with:
git archive --format=tar --remote=git.openldap.org:~git/git/openldap.git
OPENLDAP_REL_ENG_2_4 > openldap-2.4.29.tar
Or via the web with:
Sr. Member of Technical Staff
A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration