The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for pid 8426 (/usr/sbin/smbd).
Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occured. You are
encouraged to submit this information as a bug report to Debian. For
information about the procedure for submitting bug reports , please see
http://www.debian.org/Bugs/Reporting or the reportbug(1) manpage.
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 8426)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x40245808 in waitpid () from /lib/libc.so.6
#0 0x40245808 in waitpid () from /lib/libc.so.6
#1 0x402cd880 in ?? () from /lib/libc.so.6
#2 0x401de4c2 in strtold_l () from /lib/libc.so.6
#3 0x081eb261 in smb_panic2 ()
#4 0x081eb1ea in smb_panic ()
#5 0x082645e3 in smbd_server_fd ()
#6 0x082654ce in main ()
On Jun 19, 2005, at 10:53 PM, Christian Perrier wrote:
Quoting Dan Aronson ([EMAIL PROTECTED]):
Package: samba
Version: 3.0.14a-3
Severity: normal
Last night I tried to connect to a samba share for osx (Tiger
10.4.1).
I never configured samba on this new 3.1 install. Today I found lots
of email from the 'panic action' script.
Forwarding some of these as part of the bug report might help...
Doing so, please answer to the bug report and not to me.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
