Gday,
Well KDL is a acronym(abbreviation) of "Kernel Debugger Land".
When there is a serious kernel error, haiku "drops" to this KDL, one can now try and work out why the error happened.
When this happens to one, they can enter commands in the KDL to find where the error happened.
For most People, who can not understand the inside of the Haiku kernel, they can only take photographs(or screenshots if they are using vmware) of what the KDL outputs after entering respectable commands.
"BT" (back-trace) is the most handy command to work out what has gone wrong, if one gets a KDL, then they should enter that command.
In case anyone stumbles across this old thread, the KDL keystroke changed to Alt-SysRq-D (perhaps Alt-Shift-PrintScreen-D, I don't remember if both work or not).
There is also a (temporary) way to entire KDL from a terminal using the "kernel_debugger" command. That will of course likely go away in the future.
Comments
Re: What are KDL
Gday,
Well KDL is a acronym(abbreviation) of "Kernel Debugger Land".
When there is a serious kernel error, haiku "drops" to this KDL, one can now try and work out why the error happened.
When this happens to one, they can enter commands in the KDL to find where the error happened.
For most People, who can not understand the inside of the Haiku kernel, they can only take photographs(or screenshots if they are using vmware) of what the KDL outputs after entering respectable commands.
"BT" (back-trace) is the most handy command to work out what has gone wrong, if one gets a KDL, then they should enter that command.
(more info http://en.wikipedia.org/wiki/KDL )
Re: What are KDL
If You want You can open any time the KDL prompt with pressing the [Ctrl]+[Alt]+[F12] keys.
Re: What are KDL
thanks, more clear now.
Re: What are KDL
If You want You can open any time the KDL prompt with pressing the [Ctrl]+[Alt]+[F12] keys.
Actually, in Haiku right now - it's just F12 :) (although that might change in the future)
Re: What are KDL
In case anyone stumbles across this old thread, the KDL keystroke changed to Alt-SysRq-D (perhaps Alt-Shift-PrintScreen-D, I don't remember if both work or not).
There is also a (temporary) way to entire KDL from a terminal using the "kernel_debugger" command. That will of course likely go away in the future.