From owner-freebsd-current@FreeBSD.ORG Sat Aug 2 18:51:47 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F27837B401 for ; Sat, 2 Aug 2003 18:51:47 -0700 (PDT) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83F1143F93 for ; Sat, 2 Aug 2003 18:51:44 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id DF382526A3; Sun, 3 Aug 2003 11:21:41 +0930 (CST) Date: Sun, 3 Aug 2003 11:21:41 +0930 From: Greg 'groggy' Lehey To: Terry Lambert Message-ID: <20030803015141.GO95375@wantadilla.lemis.com> References: <20030802091620.GB6331@cicely12.cicely.de> <2712203.1059843659@[192.168.0.2]> <1079.192.168.0.3.1059811884.squirrel@webmail.aminor.no> <20030802090052.GA25338@rot13.obsecurity.org> <20030802091620.GB6331@cicely12.cicely.de> <1079.192.168.0.3.1059811884.squirrel@webmail.aminor.no> <20030803000528.GF95375@wantadilla.lemis.com> <3F2C601C.4EDBB33C@mindspring.com> <20030803012252.GM95375@wantadilla.lemis.com> <3F2C6718.9370DD46@mindspring.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i0LFOk513GRb+T2w" Content-Disposition: inline In-Reply-To: <3F2C6718.9370DD46@mindspring.com> User-Agent: Mutt/1.4i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: ticso@cicely.de cc: current@freebsd.org Subject: Re: Yet another crash in FreeBSD 5.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Aug 2003 01:51:47 -0000 --i0LFOk513GRb+T2w Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Saturday, 2 August 2003 at 18:36:24 -0700, Terry Lambert wrote: > Greg 'groggy' Lehey wrote: >>> The information I gave him gets him to lines of source code, instead >>> of just function names with strange hexadecimal numbers that resolve >>> to instruction offsets that may be specific to his compile flags, >>> date of checkout of the sources from CVS, etc.. >> >> The first step of the link above does the same thing. But it's only >> the first step. >>> by eyeballing the lines of source code in question and understanding >>> the code around it well enough that you can tell *how* a pointer >>> there could be NULL. My instructions *get* him those lines of >>> source. >> >> You obviously still haven't read the reference. Do that first, and >> come back when you have either understood things or are having >> difficulty understanding. But don't shoot off your mouth without >> knowing what's going on. > > I read the reference. > > How does it apply in cases like this one, where you don't have a > vmcore file? You don't seem to have read the reference very well. It also asks for other supporting information. That's the most important thing at the moment. I know that because I've been there before, and I've looked at a number of these dumps: it's almost certainly related to something he's doing which is not normal. You don't know that, and that's excusable, but it's not excusable that after four or five requests, you still haven't RTFM'd. > The way I would approach finding this, with only: > > 1) The line of code where the failure occurred > 2) The stack traceback, with no arguments > 3) The sources for the code in the stack traceback > > would be to eyeball the code in #1, and try to figure out how > I gould get to that point with that pointer having a NULL value, > given my apriori knowledge of the forward call graph. You have that? > I would examine every intermediate conditional and function call > that could effect the value of the pointer and cause it to be NULL > at the point in question. Go for it. Once I get the log files, I'll start there. > One of the details I wish you would check is whether or not he has a > vmcore file, or the ability to get one... We'll address that issue when it becomes necessary. Greg -- See complete headers for address and phone numbers --i0LFOk513GRb+T2w Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/LGqtIubykFB6QiMRAgOiAKCoUjcMx3k2xRZatGVCu5bWmpioMACglIS3 D2VpBrhQSQ9o4vBaJ7gZzdg= =pyZ/ -----END PGP SIGNATURE----- --i0LFOk513GRb+T2w--