[lkml]   [2000]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Availability of kdb
On Wed, 6 Sep 2000, Alan Cox wrote:

> > Ehh? And exactly _how_ would a debugger help it.
> >
> > Especially as Alan quoted an example of a driver bug that didn't get fixed
> > for several months because the maintainer didn't have the hardware.
> >
> > What would a debugger have done?
> Let the end user give me essential answers on what was happening at the failure
> point. Think of it as a crash dump tool with extra controls

If this is your primary argument for a kernel debugger, a 'crash dump tool
with extra controls', then why not just cleanly implement a 'crash dump
tool with extra controls'.

I would suspect that such a tool could be accomplished much much safely
(both code maintenance wise, as well as runtime and source bloat) then a full
kernel debugger. Interactive postmortem shouldn't require any support code
or tooling floating about in unrelated parts of the kernel.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.291 / U:0.544 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site