From owner-freebsd-bugs Sun Sep 12 6:19: 5 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from poseidon.dcs.napier.ac.uk (poseidon.dcs.napier.ac.uk [146.176.161.4]) by hub.freebsd.org (Postfix) with ESMTP id 02CF814A06 for ; Sun, 12 Sep 1999 06:18:25 -0700 (PDT) (envelope-from bsc4093@dcs.napier.ac.uk) Received: from artemis (artemis [146.176.161.5]) by poseidon.dcs.napier.ac.uk (8.9.3/8.9.3) with SMTP id OAA01164; Sun, 12 Sep 1999 14:17:54 +0100 (BST) Date: Sun, 12 Sep 1999 14:18:15 +0100 (BST) From: Robin Carey X-Sender: bsc4093@artemis To: John Polstra Cc: freebsd-bugs@freebsd.org Subject: Re: core dumping In-Reply-To: <199909040123.SAA10094@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 3 Sep 1999, John Polstra wrote: > In article , > Robin Carey wrote: > > > > Whilst running a very small executable, FreeBSD-3.1 decided to pump 110 > > megs of core-file into my space restricted H/D :) > > Your program must have managed to allocate that much memory before > it bit the dust. Mmmmm .... I don't think so. The program was using assert(3) - I believe this had something to do with the problem. Whilst the program/process was dumping core (took about 10 mins to complete) the core-dumping process/program would not respond to a ^C or a ^Z. I never got around to trying a kill(1) -9 .... Unrelated: cp(1) "-r" flag is not documented in the cp(1) manual page. It appears to do the same thing as "-R". > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "No matter how cynical I get, I just can't keep up." -- Nora Ephron > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message