[lkml]   [2001]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjecttesting and related tools: your opinions please
I do not work on the kernel (yet), but have read much of the fight
regarding "kdb availability." Personally, I've found the Linux Kernel
Coding Style and the tips and views Linus Torvalds provided on debugging
_extremely_ useful and _practical_ in my own work.

Your opinions on any of the following will be greatly appreciated:
What do you think of testing and related tools like gcov (that measure
which code branches are executed and the like?)

Generally, how do you maintain such level of reliability on such a huge
monolithic kernel (except by "thinking it through?")

After unit testing, does the Linux kernel rely mainly on _actual_runs_
by users/developers for testing the reliability of the whole thing?

Do you have test scripts and automated regression testing setup, or you
and Linus do not believe in that either?

Linus, if you are reading, (how) did you test the original 200K kernel
code when you were still working mostly _by_yourself_? How much did
others help with the bugs you might have left? (if any!)

Boundary conditions? How do you test them?

If anybody knows what Linus or Alan Cox might think of all this, then
please tell me too. I am interested in their opinion but they might not
respond to the message.

If relevant, please also tell me what work you do on the kernel.

I greatly appreciate your time and any insight you provide.

Reza Roboubi
Software Development Consultant

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

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