Re: The case for a standard kernel debugger

[Andrew Morton]

Frederic Magniette wrote:
> 
> This can be really awful if your code is called very often and then saturate the
> logs.

One trick you can pull is:

        if (current->uid == 9999)
                printk(stuff);

and then exercise the offending code path as user 9999.  It
works for some things.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/