Anyone seen this crash in winbindd?

[Ralph Böhme]

Hi Richard,

On Mon, Aug 21, 2017 at 07:39:54AM -0700, Richard Sharpe via samba-technical wrote:
> I did a bit of searching on the web but couldn't come up with
> anything. It looks like the memory has been deallocated out from under
> the code that was trying to take the allrecord_mutex_lock:
> 
> #0  0x00007f1831fb61d7 in __GI_raise (sig=sig at entry=6)
>     at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #1  0x00007f1831fb78c8 in __GI_abort () at abort.c:90
> #2  0x00007f18351f963b in dump_core () at ../source3/lib/dumpcore.c:322
> #3  0x00007f18351eacf7 in smb_panic_s3 (why=<optimized out>)
>     at ../source3/lib/util.c:814
> #4  0x00007f183891b12f in smb_panic (why=why at entry=0x7f18389686ab
> "internal error")
>     at ../lib/util/fault.c:166
> #5  0x00007f183891b346 in fault_report (sig=<optimized out>) at
> ../lib/util/fault.c:83
> #6  sig_fault (sig=<optimized out>) at ../lib/util/fault.c:94
> #7  <signal handler called>
> #8  0x00007f183a374e70 in __pthread_mutex_trylock (mutex=0x7f183a5a90a8)
>     at pthread_mutex_trylock.c:141

could this be bug #12455?

-slow