Date: Thu, 27 May 1999 07:55:40 -0700 From: Don Lewis <Don.Lewis@tsc.tdk.com> To: "David E. Cross" <crossd@cs.rpi.edu>, Dmitrij Tejblum <tejblum@arc.hq.cti.ru> Cc: hackers@FreeBSD.ORG Subject: Re: kernel debugging assistance Message-ID: <199905271455.HAA10808@salsa.gv.tsc.tdk.com> In-Reply-To: "David E. Cross" <crossd@cs.rpi.edu> "Re: kernel debugging assistance" (May 27, 10:32am)
next in thread | previous in thread | raw e-mail | index | archive | help
On May 27, 10:32am, "David E. Cross" wrote: } Subject: Re: kernel debugging assistance } > I don't think that this dump is useful for debugging this problem. Perhaps, if } > you compile the kernel with DEBUG_LOCKS, you will get more useful info. } > } > Dima } } I checked through the source for DEBUG_LOCKS, it doesn't appear to do anything } other than to printout information.... information that I already have access } to by way of this dump file. I will turn it on regardless swo it makes my } life a bit more simple. In some cases it sure would be nice if DEBUG_LOCKS preserved more of the stack context. Knowing that the current holder of the lock also called vop_stdlock() isn't all that useful. I'd rather know where vget() was called. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905271455.HAA10808>