From owner-freebsd-stable Sun Oct 20 8: 0:14 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E45E37B401 for ; Sun, 20 Oct 2002 08:00:12 -0700 (PDT) Received: from mtiwmhc12.worldnet.att.net (mtiwmhc12.worldnet.att.net [204.127.131.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id C63A343E88 for ; Sun, 20 Oct 2002 08:00:11 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from prime ([12.88.88.64]) by mtiwmhc12.worldnet.att.net (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with SMTP id <20021020145958.XPAL4213.mtiwmhc12.worldnet.att.net@prime> for ; Sun, 20 Oct 2002 14:59:58 +0000 Message-ID: <003a01c27849$6367d4d0$0301a8c0@prime> From: "Charles Swiger" To: References: <20021019130404.A25131-100000@edge.foundation.invalid> <001901c27798$d033df70$0301a8c0@prime> <3DB2399F.3060900@zbzoom.net> Subject: Re: 4.7-RELEASE crash [file system] Date: Sun, 20 Oct 2002 11:00:10 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Chris BeHanna wrote: > Charles Swiger wrote: [ ...taking crash dumps... ] > Reason #1 may be that some folks might not have enough space in > /var to hold one or more crash dumps (in particular, a large server > box with 4GB of RAM might easily run into this problem). A point. On the other hand, can't savecore figure out that there isn't enough space and not do the dump, then? > Reason #2 might be that a crash dump isn't of much use without a > kernel that has debugging symbols in it. Right-- but that's _my_ point. :-) People following -STABLE should be building kernels with debugging symbols, so that the members of this list have a better chance of figuring out what went wrong when a system panics. At least at one time, if you build an executable with -g, strip it & ship the binary elsewhere...then the core files generated by that stripped executable can be symbolicly debugged using the unstripped version. Has this changed? -Chuck PS: Arguably, people should be building with "-g -O" all of the time, even in production. GCC tends to generate the most reliable code for that combination of options, as those are exercised the most frequently. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message