From: Bodo Eggert <7eggert@gmx.de>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
"linux-os (Dick Johnson)" <linux-os@analogic.com>,
Adrian Bunk <bunk@kernel.org>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Building Kernel with -O0
Date: Wed, 10 Sep 2008 13:52:45 +0200 [thread overview]
Message-ID: <E1KdOFZ-0001Q4-So@be1.7eggert.dyndns.org> (raw)
In-Reply-To: <bagBJ-20J-7@gated-at.bofh.it>
linux-os (Dick Johnson) <linux-os@analogic.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.
next parent reply other threads:[~2008-09-10 11:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b8rB2-6BM-1@gated-at.bofh.it>
[not found] ` <badXc-7gl-21@gated-at.bofh.it>
[not found] ` <baf2M-bE-7@gated-at.bofh.it>
[not found] ` <bagBJ-20J-7@gated-at.bofh.it>
2008-09-10 11:52 ` Bodo Eggert [this message]
2008-09-12 5:21 ` emin ak
2008-09-12 13:23 ` linux-os (Dick Johnson)
2008-09-12 14:45 ` linux-os (Dick Johnson)
[not found] <fa.NLANnOwj/8iuI5QjLt63gFrBDJA@ifi.uio.no>
2008-09-04 23:40 ` Robert Hancock
2008-09-04 17:50 Keith A. Prickett
2008-09-09 16:04 ` Adrian Bunk
2008-09-09 17:10 ` Keith A. Prickett
2008-09-09 18:55 ` linux-os (Dick Johnson)
2008-09-09 19:24 ` Andi Kleen
2008-09-09 19:43 ` Adrian Bunk
2008-09-09 20:05 ` Andi Kleen
2008-09-09 22:24 ` David Howells
2008-09-25 13:31 ` Adrian Bunk
2008-09-25 13:51 ` David Howells
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=E1KdOFZ-0001Q4-So@be1.7eggert.dyndns.org \
--to=7eggert@gmx.de \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
/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®