[Samba] samba crashing on start up INTERNAL ERROR: Signal 11

[Sonic]

On Mon, Sep 5, 2016 at 1:58 AM, Volker Lendecke <vl at samba.org> wrote:
> What platform are you on? Can you run that under valgrind?

Gentoo, using gcc-5.4.0.

initiate_name_query_packet: sending query for name GRIZZLY<1d>
(bcast=Yes) to IP 172.27.12.255
add_response_record: adding response record id:23039 to subnet
172.27.12.66. num_records:6
==10086== Invalid read of size 4
==10086==    at 0x7C5C3C5: talloc_get_size (in /usr/lib64/libtalloc.so.2.1.8)
==10086==    by 0x5D01040: event_add_to_poll_args (events.c:92)
==10086==    by 0x12A8F0: listen_for_packets (nmbd_packets.c:1939)
==10086==    by 0x11201E: process (nmbd.c:526)
==10086==    by 0x113243: main (nmbd.c:1100)
==10086==  Address 0xffffff9f is not stack'd, malloc'd or (recently) free'd
==10086==
===============================================================
INTERNAL ERROR: Signal 11 in pid 10086 (4.4.6-GIT-28d8230)
Please read the Trouble-Shooting section of the Samba HOWTO
===============================================================
PANIC (pid 10086): internal error
BACKTRACE: 13 stack frames:
#0 /usr/local/samba/lib/libsmbconf.so.0(log_stack_trace+0x1f) [0x5ce1da1]
#1 /usr/local/samba/lib/libsmbconf.so.0(smb_panic_s3+0x6d) [0x5ce1bf2]
#2 /usr/local/samba/lib/libsamba-util.so.0(smb_panic+0x28) [0x5279004]
#3 /usr/local/samba/lib/libsamba-util.so.0(+0x20ce2) [0x5278ce2]
#4 /usr/local/samba/lib/libsamba-util.so.0(+0x20cf7) [0x5278cf7]
#5 /lib64/libpthread.so.0(+0x10d90) [0x4e47d90]
#6 /usr/lib64/libtalloc.so.2(talloc_get_size+0x5) [0x7c5c3c5]
#7 /usr/local/samba/lib/libsmbconf.so.0(event_add_to_poll_args+0x72) [0x5d01041]
#8 /usr/local/samba/sbin/nmbd(listen_for_packets+0x230) [0x12a8f1]
#9 /usr/local/samba/sbin/nmbd(+0xa01f) [0x11201f]
#10 /usr/local/samba/sbin/nmbd(main+0xe17) [0x113244]
#11 /lib64/libc.so.6(__libc_start_main+0xf0) [0x86d3720]
#12 /usr/local/samba/sbin/nmbd(_start+0x29) [0x10fe59]
dumping core in /usr/local/samba/var/cores/nmbd
==10086==
==10086== Process terminating with default action of signal 6
(SIGABRT): dumping core
==10086==    at 0x86E61D8: raise (raise.c:54)
==10086==    by 0x86E7629: abort (abort.c:89)
==10086==    by 0x5CF4DF8: dump_core (dumpcore.c:322)
==10086==    by 0x5CE1D81: smb_panic_s3 (util.c:814)
==10086==    by 0x5279003: smb_panic (fault.c:166)
==10086==    by 0x5278CE1: fault_report (fault.c:83)
==10086==    by 0x5278CF6: sig_fault (fault.c:94)
==10086==    by 0x4E47D8F: ??? (in /lib64/libpthread-2.23.so)
==10086==    by 0x7C5C3C4: talloc_get_size (in /usr/lib64/libtalloc.so.2.1.8)
==10086==    by 0x5D01040: event_add_to_poll_args (events.c:92)
==10086==    by 0x12A8F0: listen_for_packets (nmbd_packets.c:1939)
==10086==    by 0x11201E: process (nmbd.c:526)
==10086==
==10086== HEAP SUMMARY:
==10086==     in use at exit: 185,507 bytes in 960 blocks
==10086==   total heap usage: 2,417 allocs, 1,457 frees, 366,952 bytes allocated
==10086==
==10086== LEAK SUMMARY:
==10086==    definitely lost: 1,173 bytes in 1 blocks
==10086==    indirectly lost: 0 bytes in 0 blocks
==10086==      possibly lost: 74,956 bytes in 201 blocks
==10086==    still reachable: 109,378 bytes in 758 blocks
==10086==         suppressed: 0 bytes in 0 blocks
==10086== Rerun with --leak-check=full to see details of leaked memory
==10086==
==10086== For counts of detected and suppressed errors, rerun with: -v
==10086== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Aborted (core dumped)