From owner-freebsd-current@FreeBSD.ORG Sat Aug 2 18:24:40 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 09A8037B401; Sat, 2 Aug 2003 18:24:40 -0700 (PDT) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58A2643F75; Sat, 2 Aug 2003 18:24:39 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc076.dialup.mindspring.com ([209.86.0.230] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19j7bx-00008c-00; Sat, 02 Aug 2003 18:24:38 -0700 Message-ID: <3F2C641D.B18B0694@mindspring.com> Date: Sat, 02 Aug 2003 18:23:41 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Greg 'groggy' Lehey References: <1079.192.168.0.3.1059811884.squirrel@webmail.aminor.no> <3F2B803C.21D38E0B@mindspring.com> <1886375.1059842833@[192.168.0.2]> <3F2C5D2B.F8382BCA@mindspring.com> <20030803011402.GK95375@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4d1d80b8a61627e37b44c8bc99125407e350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c 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:24:40 -0000 Greg 'groggy' Lehey wrote: > > If this is repeatable for you, it's recommended that you compile > > Vinum statically into your kernel, so that you can look at the > > other symbols in the traceback and obtain source lines for them, > > as well. > > No. It is explicitly discouraged. It saves the dicking around with the .ko files. > > It may be that this will be debuggable without that information, but > > in my experience with similar problems, without a list of arguments > > to the functions from a live remote debug session and/or a > > crashdump, the problem is going to have to be found by an engineer > > eyeballing the call graph and seeing how that particular line could > > end up with a NULL in bp2 or bp. > > Terry hasn't read the debug instructions. You can load symbols from > klds. See the links I pointed to. I read them. You didn't provide examples for a non-crashdump debug session. Rather than give him incorrect information, I gave him a workaround that would guarantee that what information he did obtain would, in fact, be correct. If you would care to take over, without insisting that he be able to produce a crash dump (which he has already stated that he has had trouble doing), be my guest. The best information I can get him, without finding some way to fix his obtaining a crashdump issue (I myself have been unable to obtain one off and on during long stretches, due to the changes in that area by PHK), is to translate his ddb traceback into source code line numbers. -- Terry