[Bugs] [Bug 1207643] [geo-rep]: starting the geo-rep causes "Segmentation fault" and core is generated by "gsyncd.py"

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1207643



--- Comment #8 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/10074 committed in master by Venky Shankar
(vshankar at redhat.com) 
------
commit 00d4125a5cb7102efeb23873cbaf155a71faa9dd
Author: Kotresh HR <khiremat at redhat.com>
Date:   Tue Mar 31 20:13:59 2015 +0530

    libgfchangelog: Use correct 'this' pointer on new thread creation

    When libgfchangelog is linked with non xlator application,
    it should point to 'master' xlator which is initiated separately.
    When ever a new thread is created, 'THIS' points to the global
    xlator. 'THIS' should point to corresponding xlator even then.
    This patch adjusts the pointer accordingly.

    Change-Id: I2a199bb3c73146a0329540aedcbae697a00f6f0a
    BUG: 1207643
    Signed-off-by: Kotresh HR <khiremat at redhat.com>
    Reviewed-on: http://review.gluster.org/10074
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar at redhat.com>
    Tested-by: Venky Shankar <vshankar at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=nem15Q00tX&a=cc_unsubscribe