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 majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
