On Wed, 6 Sep 2000, Dan Hollis wrote:
> On Wed, 6 Sep 2000, Alan Cox wrote:
> > For things like driver debugging its the only way to work. Hardware simply does
> > not work like the manual says and no amount of Zen contemplation will ever
> > make you at one with a 3c905B ethernet card.
>
> This is probably the best argument for a kernel debugger.
>
> Adding debug code (printk, if/then/BUG() etc) to track down a driver bug
> sometimes changes behaviour enough to turn it into a heisenbug. In these
> cases a kernel debugger is the best way to swat it.
I've found the opposite more times than not. The debugger leaves
too many zeroes around, leading to code that doesn't fail when run
under the debugger.
Mike
-
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/
