On Sunday, 23 April 2000 at 18:25:28 +0200, Mark Huizer wrote:
> On Sun, Apr 23, 2000 at 11:42:18AM +0930, Greg Lehey wrote:
>> On Thursday, 13 April 2000 at 13:20:50 +0200, Mark Huizer wrote:
>>> Hi
>>>
>>> I'm trying to debug a kernel that is not crashing but hanging, with all
>>> processes in 'inode' wchan. So I did a 'call panic()', and now I have
>>> the crashdump, but is there a way to get to the data structures of the
>>> kernel???
>>
>> Sure. What are you looking for? Have you read the section on kernel
>> debugging in the handbook?
>
> Yep, done that kind of stuff before, but never on non-crashing kernels
> :-( Problem is I want to get at the stacks of various running processes,
> and the syscalls they are making.
> I started using the vinum gdb macros, which got me a bit further,
> though not yet enough, I'm afraid.
What are you missing? You can get a stack trace, but you'll have to
go looking for the variables yourself.
Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
