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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0809120918570.7332@chaos.analogic.com>
Date:	Fri, 12 Sep 2008 09:23:16 -0400
From:	"linux-os (Dick Johnson)" <linux-os@...logic.com>
To:	"emin ak" <eminak71@...il.com>
Cc:	"Adrian Bunk" <bunk@...nel.org>,
	"Linux kernel" <linux-kernel@...r.kernel.org>, <7eggert@....de>
Subject: Re: Building Kernel with -O0

On Fri, 12 Sep 2008, emin ak wrote:

> 2008/9/10 Bodo Eggert <7eggert@....de>:
>> 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.
>>
>> --
>
> I had compiled linux-2.6.23 with -O0 for kgdb only with little
> modifications, it's  running with no error for a long time. I'am not a
> linux expert, I think talented kernel hackers can make kernel to
> compile with -O0 easly but for some reason they dont want to do it.
> Debug is much understandable for me (and for most people I think) with
> -O0. Linux kernel programming ability is not a gift, of course you can
> learn the code with printks and reading, but which age are we living
> in?
>
> Emin
>

Well, to use the ** kernel ** to single-
step through the ** kernel ** is
really not going to be much more than an
exercise. It's not going to find the bugs
that are likely to exist in kernel code.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.25.17 on an i686 machine (4786.38 BogoMips).
My book : http://www.AbominableFirebug.com/
_

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@...logic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
--
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/