hi Atin, Kaushal,
Is this a known issue?
(gdb) #1 0xbb789fb7 in __synclock_unlock (lock=0xbb1d4ac0)
(gdb) at
/home/jenkins/root/workspace/rackspace-netbsd7-regression-triggered/libglusterfs/src/syncop.c:1056
#2 0xbb789ffd in synclock_unlock (lock=0xbb1d4ac0)
at
Not that I am aware of. Do you have backtrace of all the threads?
~Atin
On 02/10/2016 05:58 PM, Pranith Kumar Karampuri wrote:
> hi Atin, Kaushal,
> Is this a known issue?
>
> (gdb) #1 0xbb789fb7 in __synclock_unlock (lock=0xbb1d4ac0)
> (gdb) at
>
On 02/10/2016 06:01 PM, Atin Mukherjee wrote:
Not that I am aware of. Do you have backtrace of all the threads?
it doesn't seem to give proper output for 'thread apply all bt':
(gdb) thread apply all bt
Thread 6 (process 2):
#0 0xbb354977 in ?? ()
#1 0xbb682b67 in ?? ()
#2 0xba4fff98 in
On Wed, Feb 10, 2016 at 6:08 PM, Pranith Kumar Karampuri
wrote:
>
>
> On 02/10/2016 06:01 PM, Atin Mukherjee wrote:
>>
>> Not that I am aware of. Do you have backtrace of all the threads?
>
>
> it doesn't seem to give proper output for 'thread apply all bt':
> (gdb) thread
On 02/10/2016 06:13 PM, Kaushal M wrote:
> On Wed, Feb 10, 2016 at 6:08 PM, Pranith Kumar Karampuri
> wrote:
>>
>>
>> On 02/10/2016 06:01 PM, Atin Mukherjee wrote:
>>>
>>> Not that I am aware of. Do you have backtrace of all the threads?
>>
>>
>> it doesn't seem to give