From owner-freebsd-current Tue Jul 31 5: 0:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id C0EF837B401; Tue, 31 Jul 2001 05:00:28 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15RYDL-0000my-00; Tue, 31 Jul 2001 14:01:31 +0200 From: Sheldon Hearn To: jhb@FreeBSD.org Cc: current@FreeBSD.org Subject: Re: Help wanted: loadable SMBFS In-reply-to: Your message of "Mon, 30 Jul 2001 00:00:53 +0200." <2572.996444053@axl.seasidesoftware.co.za> Date: Tue, 31 Jul 2001 14:01:31 +0200 Message-ID: <3035.996580891@axl.seasidesoftware.co.za> 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 [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? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message