From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Dragoslav Zaric <dragoslav.zaric.kd@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Debug only with printk ?
Date: Wed, 29 Apr 2009 13:15:54 -0400 [thread overview]
Message-ID: <20090429171553.GC21465@csclub.uwaterloo.ca> (raw)
In-Reply-To: <2d05c4580904281427r65282bb2m5dd8c9f8a2de5363@mail.gmail.com>
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
prev parent reply other threads:[~2009-04-29 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 21:27 Dragoslav Zaric
2009-04-29 3:15 ` Valdis.Kletnieks
2009-04-29 17:15 ` Lennart Sorensen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090429171553.GC21465@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=dragoslav.zaric.kd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®