From owner-freebsd-current Tue Jul 31 8:45:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id AD53C37B405 for ; Tue, 31 Jul 2001 08:45:35 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.217]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id IAA27157; Tue, 31 Jul 2001 08:45:34 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3035.996580891@axl.seasidesoftware.co.za> Date: Tue, 31 Jul 2001 08:45:21 -0700 (PDT) From: John Baldwin To: Sheldon Hearn Subject: Re: Help wanted: loadable SMBFS Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 31-Jul-01 Sheldon Hearn wrote: > > [Aside: problems getting crashdumps resolved, see message with ] > [Message-ID <2764.996580117@axl.seasidesoftware.co.za> sent to -current] > [with subject "Re: -current lockups". ] > > On Mon, 30 Jul 2001 00:00:53 +0200, Sheldon Hearn wrote: > >> I got a little help from some folks on IRC who helped me with a >> disassembly that confirms a null pointer dereference in the >> STAILQ_REMOVE(). > > Hi John, > > So now that I have crashdumps working (thanks!), I've got a populated > ktr_buf in my crashdump. > > Sadly, I don't understand much of what's in it. Is there a magic "look > for this" to find where 90rql (the smbfs request lock) got accidentally > removed from all_locks, or does this require intelligence? > > If so, do I send you the output of Greg Lehy's "ktr" GDB macro? What's > standard procedure with these things? If it works. :) It may need updating to work right. Basically the KTR buffer is kind of like a printf buffer. Various points in the code stuff messages into it when an event happens (such as getting a lock, releasing a lock, etc.) There should be an event right at the end about the lock in question being destroyed for example (if you had KTR_LOCK turned on). You might then look in the logs to see where else the same lock was messed with. > Ciao, > Sheldon. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message