linux-kernel - Re: Building Kernel with -O0

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: <E1KdOFZ-0001Q4-So@be1.7eggert.dyndns.org>
Date:	Wed, 10 Sep 2008 13:52:45 +0200
From:	Bodo Eggert <7eggert@....de>
To:	"linux-os (Dick Johnson)" <linux-os@...logic.com>,
	"linux-os (Dick Johnson)" <linux-os@...logic.com>,
	Adrian Bunk <bunk@...nel.org>,
	Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: Building Kernel with -O0

linux-os (Dick Johnson) <linux-os@...logic.com> wrote:

> If you have to single-step through kernel procedures, you
> are not writing proper code for a kernel. Furthermore, even
> when using the kernel debugger, you are not executing the
> exact same path that would be executed without the debugger
> attached.

I sometimes single-step in order to verify my (userspace) code, instead of
just throwing random test data at it. It's easier and makes me feel better.
OTOH, -O2 never was a problem if I used it, so I don't strongly vote
for enabling -O0.

--
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/