From owner-freebsd-stable@FreeBSD.ORG Thu May 27 17:53:26 2004 Return-Path: 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 63F0316A4CE; Thu, 27 May 2004 17:53:26 -0700 (PDT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2419A43D2D; Thu, 27 May 2004 17:53:25 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from [10.0.2.5] (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id i4S0pjas006214; Fri, 28 May 2004 10:21:53 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Robert Watson In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-V5qowGaoU/dKxg3jbEXt" Organization: Genesis Software Message-Id: <1085705504.977.118.camel@inchoate.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 27 May 2004 14:51:44 -1000 X-Spam-Score: -2.2 () IN_REP_TO,NOSPAM_INC,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01 X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: stable@freebsd.org cc: David Magda Subject: Re: how to interpret crash? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 May 2004 00:53:26 -0000 --=-V5qowGaoU/dKxg3jbEXt Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2004-05-27 at 13:55, Robert Watson wrote: > I don't debate your basic point that on a stable system, you're least > likely to find the symbols when you most need them, as the system will ru= n > fine for a long time and then run into some edge case, unusual hardware > failure mode, or whatever, and given that it's been stable for years, you > will find yourself with little debugging recourse. That's where tricks > like using nm to track down the symbols, turning on dumps by default, > compiling with the necessary DDB bits to generate a stack trace, etc, can > come in quite handy. I think turning on dumps by default is a good habit for sys admins to get into :) If the system dies and cores then you can rebuild your kernel with debugging symbols and see where it died. At least that's _supposed_ to work from what I've heard :) --=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --=-V5qowGaoU/dKxg3jbEXt Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAto0g5ZPcIHs/zowRAiSuAJ9L5MhHAwd838Xo+IPnOpVFIEV7AACfeoYZ aIKdsksrQKrHaFaG2tpT/54= =/Aex -----END PGP SIGNATURE----- --=-V5qowGaoU/dKxg3jbEXt--