DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=Jza7yoL3nwHNVwYFn1KYStpyfAYwKMPN1NBkWuj+odlkGxk2GANrTytL4/azfys55R
         W1oHu1aAW4CZgMgNyGmqF5uEPOYZoSZyPzX21QvKg7HlIQhN79TF0QuJLZjO86K40Cpl
         YUudCiaZVREISB7EPsMpNpvK9+d0yX4kLchmo=
MIME-Version: 1.0
Date: Tue, 28 Apr 2009 23:27:42 +0200
Message-ID: <2d05c4580904281427r65282bb2m5dd8c9f8a2de5363@mail.gmail.com>
Subject: Debug only with printk ?
From: Dragoslav Zaric <dragoslav.zaric.kd@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 779
Lines: 22

Hello,

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 ?

thanks

Dragoslav Zaric
[Programmer; M Sc Astrophysics]
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/