Well-known Haiku kernel hacker Ingo Weinhold has written an in-depth guide to using the Haiku kernel debugger. It describes the most important commands, introduces the recently added kernel tracing feature, and concludes with an example KDL session in which Ingo debugs an inter application deadlock. A recommended read, especially if you are a Haiku hacker or interested in becoming one.
‘Welcome to Kernel Debugging Land’
Submitted by stippi 2008-02-04 Haiku 7 Comments
> It describes the most important commands
Then where is kdlhangman cited ?
Hopefully ppl will be less afraid of KDL now
If only I had this info when I was trying to debug my sound driver for BeOS. I think Haiku is going to be fun to program for.
Kernel debugging is pretty fun. It’s like diagnosing a patient through an autopsy or exploratory surgery. You can’t see everything (particularly, dynamic behavior is nearly impossible to capture without extensive tracing or something like DTrace), so you have to make hypotheses and see if the state you see in the debugger matches. It’s also an interesting challenge to find the correct place to put a breakpoint so that you get only the path you’re interested in and not some other path. It’s hard to get started on this, though, unless you have enough knowledge of the system you want to debug and some specific issue to attack.