Re: Debug only with printk ?

[Lennart Sorensen]

On Tue, Apr 28, 2009 at 11:27:42PM +0200, Dragoslav Zaric wrote:
> I am relatively new in linux kernel and since debugging is key
> element of programming, I am wondering is it really necessary
> to use various debugging tools for kernel debugging ?
> 
> Is simple printing with printk enough to debug any kind of kernel problem,
> and if not, what are the cases when printk is not enough ?
> 
> Also, is there possibility when using debugging tools to affect
> kernel environment, because debugging tool will also take cpu time and
> memory resources ?

So far I have used printk's, parsing of the OOPS when I do something
stupid, educated guesing looking at the code following an OOPS or other
problem, and in a couple of cases using firescope.  I have used firescope
to monitor the DMA ring buffer for the pcnet32 driver once.

-- 
Len Sorensen
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/