Bug#203340: marked as done (Segfault in Samba)
Your message dated Thu, 21 Oct 2004 10:56:58 +0900
with message-id <81vfd4ygt1.wl@omega.webmasters.gr.jp>
and subject line Bug#203340: Processed: Re: Bug#203340: Segfault in Samba
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 29 Jul 2003 13:36:56 +0000
>From admin@mbjk.pl Tue Jul 29 08:36:51 2003
Return-path: <admin@mbjk.pl>
Received: from pa170.przezmierowo.sdi.tpnet.pl (slonko.mbjk.pl) [217.96.162.170]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19hUen-0005j1-00; Tue, 29 Jul 2003 08:36:49 -0500
Received: from jowisz (unknown [192.168.1.3])
by slonko.mbjk.pl (Postfix) with ESMTP id 178BD1874E8
for <submit@bugs.debian.org>; Tue, 29 Jul 2003 15:33:22 +0200 (CEST)
Message-ID: <000601c355d6$7ba6ff10$0301a8c0@jowisz>
From: "Admin MBJK.PL" <admin@mbjk.pl>
To: <submit@bugs.debian.org>
Subject: Segfault in Samba
Date: Tue, 29 Jul 2003 15:36:57 +0200
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0
tests=HAS_PACKAGE
version=2.53-bugs.debian.org_2003_07_20
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_07_20 (1.174.2.15-2003-03-30-exp)
Package: Samba
Version 3.0BETA2-1
To generuje samba i wysyla mi na roota:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for pid 5505 (/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)...(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)...
(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)...0x4023eaf9 in wait4 () from /lib/libc.so.6
#0 0x4023eaf9 in wait4 () from /lib/libc.so.6
#1 0x402b1f60 in sys_sigabbrev () from /lib/libc.so.6
#2 0xbffff514 in ?? ()
#3 0x4023eaab in waitpid () from /lib/libc.so.6
#4 0x401e16da in strtold_l () from /lib/libc.so.6
#5 0x401e17dd in system () from /lib/libc.so.6
#6 0x0817eac5 in smb_panic ()
#7 0x081700e2 in dbgtext ()
#8 <signal handler called>
#9 0x403ffacd in _nss_files_gethostbyaddr_r () from /lib/libnss_files.so.2
#10 0x40277647 in gethostbyaddr_r () from /lib/libc.so.6
#11 0x4027744a in gethostbyaddr () from /lib/libc.so.6
#12 0x08181de9 in get_socket_name ()
#13 0x08175d80 in check_access ()
#14 0x080b6cbc in process_smb ()
#15 0x080b7578 in smbd_process ()
#16 0x081d5140 in main ()
#17 0x401baa51 in __libc_start_main () from /lib/libc.so.6
#18 0x08075fa5 in _start ()
---------------------------------------
Received: (at 203340-done) by bugs.debian.org; 21 Oct 2004 01:57:00 +0000
>From gotom@debian.or.jp Wed Oct 20 18:57:00 2004
Return-path: <gotom@debian.or.jp>
Received: from omega.webmasters.gr.jp (webmasters.gr.jp) [218.44.239.78]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CKSCK-0007yb-00; Wed, 20 Oct 2004 18:57:00 -0700
Received: from omega.webmasters.gr.jp (localhost [127.0.0.1])
by webmasters.gr.jp (Postfix) with ESMTP id 7CFF1DECC8
for <203340-done@bugs.debian.org>; Thu, 21 Oct 2004 10:56:59 +0900 (JST)
Date: Thu, 21 Oct 2004 10:56:58 +0900
Message-ID: <81vfd4ygt1.wl@omega.webmasters.gr.jp>
From: GOTO Masanori <gotom@debian.or.jp>
To: 203340-done@bugs.debian.org
Subject: Re: Bug#203340: Processed: Re: Bug#203340: Segfault in Samba
In-Reply-To: <818ydqf5ee.wl@omega.webmasters.gr.jp>
References: <20030802041341.GA17714@quetzlcoatl.dodds.net>
<handler.s.C.105979762822660.transcript@bugs.debian.org>
<811xjpgsj4.wl@omega.webmasters.gr.jp>
<20040709204253.GU13137@dodds.net>
<818ydqf5ee.wl@omega.webmasters.gr.jp>
User-Agent: Wanderlust/2.9.9 (Unchained Melody) SEMI/1.14.3 (Ushinoya)
FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2
(i386-debian-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Delivered-To: 203340-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
At Mon, 12 Jul 2004 09:14:33 +0900,
GOTO Masanori wrote:
> What the status of this bug? Is this bug reproducible? Both glibc
> and samba have been upgraded, and there's no report like this bug. So
> I guess this bug can be closed nowadays. If you have no problem, and
> if you no objection, I would like to close it. If not, please report
> us this bug in detail.
No one reports it, so I think this bug is already fixed. I close this
bug.
Regards,
-- gotom
Reply to: