[lkml]   [2000]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Availability of kdb
> Apparently, if you follow the arguments, not having a kernel debugger
> leads to various maladies:
> - you crash when something goes wrong, and you fsck and it takes forever
> and you get frustrated.

'It crashed.'
[Spend hour teaching and end user to patch kdb]
'It crashed, it says foo, but this fsck took hours so I dont have time to help

[Bug goes unfixed for 2 months because it only happens on a revision 8 card
which the maintainer doesnt]

> - people have given up on Linux kernel programming because it's too hard
> and too time-consuming

Programming isnt the problem to me - its debugging. I get a lot of awful patches
that have good debugging behind them. That debugging is the valuable part. I
used to reach each of Andrea's patches to find out what the bug was rather than
how he fixed it for example (nowdays I tend to apply his patches of course)

For things like driver debugging its the only way to work. Hardware simply does
not work like the manual says and no amount of Zen contemplation will ever
make you at one with a 3c905B ethernet card.

In many ways good crash dump tools and tracebacks (oopses do not count) are
the valuable bit - remote gdb happens to be a passable crash dump tool


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.615 / U:0.660 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site