> I agree, but the intent is replacing a debugging method with another > debugging method (hoping it is more useful). The messages showed here > are the same that the ones which would be shown on the console before > the diff.
the thing about the kernel messages, is you see the pointers and you know to go fix the code. The problem with hiding it in some optional-visibility interface, is that these things may show up without the more paranoid developers noticing the problem. How do we prevent non-#define DEBUG_FOO situations from growing?
