I hold the opinion that unless it is really hindering your "movements"
in the code, debugging code should remain in place. At some point in
the future, you're going to get a problem, where enabeling the
debugging code leads you to the problem quickly, while having to redo
the debugging stuff takes a while.
Linux also has a lot of stuff that checks for stuff that "usually
doesn't go wrong". For example pushing data on skbuffs check if that
space is available. You could argue that Linux has been debugged
enough that this is no longer neccesary, but I tell you that it is
much nicer to get a reproducable kernel panic while developing a
driver than it is to have clients wine about unstable software.
And I bet I'd have forgotten to turn that debugging on before starting
developing, as well as I'd think stuff was stable before shipping, so
the field would see "unstable behaviour" instead of the reliable
panic. So Linux indeed has some debugging code, that remains enabled
even in production kernels. This means that the cause for problems is
more easily traced. This is a feature.
Roger.
-- Actor asks a collegue: "To what do you owe your success in acting?" Answer: "Honesty. Once you've learned how to fake that, you've got it made." -------- Custom Linux device drivers for sale! Call for a quote. ---------- Email: R.E.Wolff@BitWizard.nl || Tel: +31-15-2137555 || FAX: +31-15-2138217- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu