From owner-freebsd-bugs  Thu Jan 18 22:00:38 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA10851
          for bugs-outgoing; Thu, 18 Jan 1996 22:00:38 -0800 (PST)
Received: from birk04.studby.uio.no (birk04.studby.uio.no [129.240.214.13])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA10846
          for <freebsd-bugs@freebsd.org>; Thu, 18 Jan 1996 22:00:35 -0800 (PST)
Received: (from aagero@localhost) by birk04.studby.uio.no (8.7.3/Himkok) id HAA02588; Fri, 19 Jan 1996 07:00:21 +0100 (MET)
Date: Fri, 19 Jan 1996 07:00:21 +0100 (MET)
Message-Id: <199601190600.HAA02588@birk04.studby.uio.no>
From: Åge Røbekk <aagero@aage.aage.priv.no>
To: freebsd-bugs@freebsd.org
Subject: coredumps get funny names
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Sender: owner-bugs@freebsd.org
Precedence: bulk


In -current, coredumps often get a strange name, probably due to a
uninitialized buffer:

$ sleep 10^\Quit (core dumped)
$ ls -l "sleep.core=98=F0^J" (tab expansion)

My guess is that name[] in +1206 /sys/kern/kern_sig.c should be
bzero'd or memset or something.

-aage