[Gluster-devel] Running glusterd with valgrind

[Avra Sengupta]

Hi Samikshan,

I found the crash on RHEL 6.5, and it's constantly reproducible on my 
setup.

Regards,
Avra

On 09/15/2016 06:21 PM, Samikshan Bairagya wrote:
>
>
> On 09/15/2016 03:48 PM, Avra Sengupta wrote:
>> Hi,
>>
>> I was trying to run valgrind with glusterd using the following command:
>>
>> valgrind --leak-check=full --log-file=/tmp/glusterd.log glusterd
>>
>> This command used to work before, rather seamlessly but now glusterd
>> crashes with the following bt:
>>
>> /usr/local/lib/libglusterfs.so.0(_gf_msg_backtrace_nomem+0x9c)[0x4c3772c] 
>>
>> /usr/local/lib/libglusterfs.so.0(gf_print_trace+0x314)[0x4c426f4]
>> /lib64/libc.so.6[0x3344a329a0]
>> /lib64/libc.so.6(gsignal+0x35)[0x3344a32925]
>> /lib64/libc.so.6(abort+0x175)[0x3344a34105]
>> /lib64/libc.so.6[0x3344a2ba4e]
>> /lib64/libc.so.6(__assert_perror_fail+0x0)[0x3344a2bb10]
>> /usr/lib64/liburcu-bp.so.1(rcu_bp_register+0x288)[0xf7974a8]
>> /usr/lib64/liburcu-bp.so.1(rcu_read_lock_bp+0x4e)[0xf79751e]
>> /usr/local/lib/glusterfs/3.10dev/xlator/mgmt/glusterd.so(+0x10e07e)[0xf52e07e] 
>>
>>
>> /usr/local/lib/glusterfs/3.10dev/xlator/mgmt/glusterd.so(+0x619cb)[0xf4819cb] 
>>
>>
>> /usr/local/lib/glusterfs/3.10dev/xlator/mgmt/glusterd.so(+0x62394)[0xf482394] 
>>
>>
>> /usr/local/lib/libglusterfs.so.0(synctask_wrap+0x10)[0x4c70a50]
>> /lib64/libc.so.6[0x3344a43bf0]
>>
>> Is this a known issue? Is there another way to run gluster with 
>> valgrind.
>>
>
> Hey Avra,
>
> Don't think its a known issue. I tried reproducing this on RHEL7 and 
> Fedora24 machines with gluster built against current updated master; 
> but I didn't hit this crash. Which distro are you getting this issue on?
>
> Regards,
> Samikshan
>
>
>> Regards,
>> Avra
>> _______________________________________________
>> Gluster-devel mailing list
>> Gluster-devel at gluster.org
>> http://www.gluster.org/mailman/listinfo/gluster-devel