From owner-freebsd-current@FreeBSD.ORG  Sun Sep  5 13:37:50 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1FB5516A4CE
	for <current@freebsd.org>; Sun,  5 Sep 2004 13:37:50 +0000 (GMT)
Received: from happy.kiev.ua (happy.kiev.ua [193.109.241.145])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4459C43D1F
	for <current@freebsd.org>; Sun,  5 Sep 2004 13:37:49 +0000 (GMT)
	(envelope-from gul@happy.kiev.ua)
Received: from gul by happy.kiev.ua with local (Exim 4.41)
	id 1C3xDF-0005xv-BT
	for current@freebsd.org; Sun, 05 Sep 2004 16:37:45 +0300
Date: Sun, 5 Sep 2004 16:37:45 +0300
From: Pavel Gulchouck <gul@gul.kiev.ua>
To: current@freebsd.org
Message-ID: <20040905133744.GZ3280@happy.kiev.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: Linux
X-FTN-Address: 2:463/68
X-Flames-To: /dev/null
X-GC: GCC d- s+: a33 C+++ UL++++ UB++++ P+ L++ E--- W++ N++ o-- K- w--- O++
X-GC: M? V- PS PE+ Y+ PGP+ t? 5? X? R? !tv b+ DI? D? G e h--- r+++ y+++
User-Agent: Mutt/1.5.6i
Subject: fstat segfault
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: gul@gul.kiev.ua
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2004 13:37:50 -0000

Hello.

I've found messages like
kernel: pid 92857 (fstat), uid 1016: exited on signal 11
on my syslog. On this machine fstat runs every 5 minutes
by mrtg. Simple test gives this result:

root@new-puma:~>while fstat >/dev/null; do echo -n '#'; done
############################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################Segmentation fault

It gets segfault on SMP systems, 5.3-BETA2 and 5.2.1-RELEASE-p9
and works correctly on single-cpu systems, but I'm not sure it's
a common rule.

Here's gdb output:

Program received signal SIGSEGV, Segmentation fault.
0x281453fd in bcopy () from /lib/libc.so.5
(gdb) bt
#0  0x281453fd in bcopy () from /lib/libc.so.5
#1  0x08049488 in dofiles (kp=0x8051ca8) at /usr/src/usr.bin/fstat/fstat.c:372
#2  0x08049228 in fstat_kvm (what=0, arg=0)
    at /usr/src/usr.bin/fstat/fstat.c:278
#3  0x08049264 in fstat_sysctl (what=0, arg=0)
    at /usr/src/usr.bin/fstat/fstat.c:289
#4  0x08048f83 in main (argc=1, argv=0xbfbfeb1c)
    at /usr/src/usr.bin/fstat/fstat.c:229

Any ideas?

-- 
                                Lucky carrier,
                                                  Pavel.