From owner-freebsd-hackers Fri Jul 28 8: 4:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 4AA9937C1D8 for ; Fri, 28 Jul 2000 08:04:52 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.9.3/8.9.3) id LAA27583 for hackers@freebsd.org; Fri, 28 Jul 2000 11:07:09 -0400 (EDT) (envelope-from dufault) From: Peter Dufault Message-Id: <200007281507.LAA27583@hda.hda.com> Subject: core dumps when mmap'd to large sparse files To: hackers@freebsd.org Date: Fri, 28 Jul 2000 11:07:04 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a program where I mmap a huge sparse file. If I fault and generate a core dump it proceeds to do something until the disk is full, but the disk is then left not full and a perfectly good core dump of a reasonable size is left. Can anyone explain? This is with 4.0. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message