Date: Tue, 31 Jul 2001 14:01:31 +0200 From: Sheldon Hearn <sheldonh@starjuice.net> To: jhb@FreeBSD.org Cc: current@FreeBSD.org Subject: Re: Help wanted: loadable SMBFS Message-ID: <3035.996580891@axl.seasidesoftware.co.za> In-Reply-To: Your message of "Mon, 30 Jul 2001 00:00:53 %2B0200." <2572.996444053@axl.seasidesoftware.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
[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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3035.996580891>