From owner-freebsd-questions Tue Mar 14 8:29:52 2000 Delivered-To: freebsd-questions@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id DDB6137B6CF for ; Tue, 14 Mar 2000 08:29:47 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12UuCQ-0000pM-00; Tue, 14 Mar 2000 18:29:38 +0200 From: Sheldon Hearn To: "Mitch Vincent" Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Corefile size.. In-reply-to: Your message of "Tue, 14 Mar 2000 11:21:07 EST." <01f701bf8dd1$4d6e0380$40ee2fd8@venux.net> Date: Tue, 14 Mar 2000 18:29:38 +0200 Message-ID: <3183.953051378@axl.ops.uunet.co.za> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Mar 2000 11:21:07 EST, "Mitch Vincent" wrote: > I guess I've just looked over this in my attempts to find it in some > documentation somewhere, how does one go about setting the corefile size in > FreeBSD (3.4)? I have something segfaulting yet it leaves a core file with a > file size of zero -- always. Setting the corefile size to zero is the correct thing to do. I know that a bug which led to zero size core files was fixed in the last few months, but can't remember in which branches, nor exactly when. I'd advise trying to upgrade to a recent 3.4-STABLE (if you're not interested in 4.0-RELEASE, of course). If it's not fixed in a recent 3.4-STABLE, file a PR using send-pr(1) and bug me about it. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message