Bug 9825 - intermittent core dump with smbstatus
Summary: intermittent core dump with smbstatus
Status: NEW
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: File services (show other bugs)
Version: 4.0.4
Hardware: x64 Linux
: P5 major (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
Depends on:
Reported: 2013-04-23 00:15 UTC by sanved
Modified: 2014-01-27 17:29 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description sanved 2013-04-23 00:15:30 UTC
Environment is debian wheezy x64 running on netgear 6 with samba 4.0.4

Intermittently when i run smbstatus i get a core dump generated by smbstatus

I will investigate more just wanted to file it for now

warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `smbstatus'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007fcd589b4103 in ?? () from /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so
(gdb) bt
#0  0x00007fcd589b4103 in ?? () from /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so
#1  0x00007fcd589d2485 in ?? () from /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so
#2  0x00007fcd5928f794 in ?? () from /usr/lib/x86_64-linux-gnu/samba/libdbwrap.so
#3  0x00007fcd565261c7 in ?? () from /usr/lib/x86_64-linux-gnu/libtdb.so.1
#4  0x00007fcd5652633b in tdb_traverse_read () from /usr/lib/x86_64-linux-gnu/libtdb.so.1
#5  0x00007fcd5928fac9 in ?? () from /usr/lib/x86_64-linux-gnu/samba/libdbwrap.so
#6  0x00007fcd5928d61a in dbwrap_traverse_read () from /usr/lib/x86_64-linux-gnu/samba/libdbwrap.so
#7  0x00007fcd589d5014 in smbXsrv_session_global_traverse () from /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so
#8  0x00007fcd589b424c in sessionid_traverse_read () from /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so
#9  0x0000000000403df0 in main ()
Comment 1 Arvid Requate 2014-01-27 17:29:14 UTC
This smells like Bug 10003. Without a proper backtrace including debug symbols it's hard to tell.