linux-kernel - Debug only with printk ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <2d05c4580904281427r65282bb2m5dd8c9f8a2de5363@mail.gmail.com>
Date:	Tue, 28 Apr 2009 23:27:42 +0200
From:	Dragoslav Zaric <dragoslav.zaric.kd@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: Debug only with printk ?

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/