Date: Sat, 02 Sep 2000 15:58:50 -0600
From: "Jeff V. Merkey" <email@example.com>
I can only assume the reason for this is one of control, and that
there are no valid technical reasons for it. I have spent more
nights with printk() than I care to.
And I bet the lessons learned and the issues involved in those nights
with printk will never leave your brain, you will remember precisely
in the future next time you see the same types of symptoms what kinds
of things to look for and where.
This is what a debugger does not do for you. The debugger allows you
to be lazy, step around, "oh yeah check for NULL" and never have to
_think_ about what you're doing or the changes you're making or even
if the same bug might be elsewhere.
This is why Linus does not allow a debugging facility like this into
the kernel, so people spend time _thinking_ when they go hunting down
It takes longer to nail a bug, yes, but the resulting fix is always
far superior. And the person who discovers the bug leaves with a much
larger amount of knowledge about how that area of the kernel works.
David S. Miller
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Sep 07 2000 - 21:00:20 EST