Hi,

I've got the same behavior. Samba panic action has produced the following backtrace:

[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
0xb7790424 in __kernel_vsyscall ()
#0  0xb7790424 in __kernel_vsyscall ()
#1  0xb6cc53c3 in waitpid () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#2  0xb6c4ca08 in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#3  0xb7771a7b in system () from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
#4  0xb71f241a in smb_panic_s3 () from /usr/lib/i386-linux-gnu/libsmbconf.so.0
#5  0xb774954a in smb_panic () from /usr/lib/i386-linux-gnu/libsamba-util.so.0
#6  0xb75578ae in ?? () from /usr/lib/i386-linux-gnu/samba/libsmbd_base.so.0
#7  0xb7557c31 in smbd_exit_server () from 
/usr/lib/i386-linux-gnu/samba/libsmbd_base.so.0
#8  0xb7146972 in exit_server () from 
/usr/lib/i386-linux-gnu/samba/libsmbd_shim.so.0
#9  0xb77b713b in main ()


I hope it could help.

Adrien


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to