From owner-freebsd-current  Thu Apr 20 08:35:50 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id IAA00484
          for current-outgoing; Thu, 20 Apr 1995 08:35:50 -0700
Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA00478
          for <current@freebsd.org>; Thu, 20 Apr 1995 08:35:48 -0700
Received: from utis156.cs.utwente.nl by utrhcs.cs.utwente.nl (5.0/csrelayMX-SVR4_1.0/RB)
	id AA13272; Thu, 20 Apr 1995 17:35:45 --100
Received: by utis156.cs.utwente.nl (4.1/RBCS-1.0.1)
	id AA14716; Thu, 20 Apr 95 17:35:38 +0200
To: current@FreeBSD.org
Subject: Re: Programs using kmem always dump core 
In-Reply-To: Your message of Thu, 20 Apr 1995 13:12:08 +0200
Date: Thu, 20 Apr 1995 17:35:37 +0200
Message-Id: <14715.798392137@utis156.cs.utwente.nl>
From: Andras Olah <olah@cs.utwente.nl>
content-length: 542
Sender: current-owner@FreeBSD.org
Precedence: bulk

On Thu, 20 Apr 1995 13:12:08 +0200, Andras Olah wrote:
> Programs that use kvm (e.g. ifconfig, savecore, kvm_mkdb at bootup,
> but also netstat or ps) dump core on my current machine.  I've

I've found the (partial) solution in an earlier posting of Bruce.  A
week ago he wrote about an mmap() bug which causes stripped kernels
to have an invalid symbol table.  Until now I've used kernels which
were 'config -g' -ed and then I 'strip -x' -ed them before
installation.  I compiled a kernel without -g and there're no more
core dumps.

Andras