From: Hui Zhu <teawater@gmail.com>
To: Steven <mqyoung@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
linux-kernel@vger.kernel.org,
Michael Snyder <msnyder@vmware.com>,
Marc Khouzam <marc.khouzam@ericsson.com>,
Thiago Jung Bauermann <thiago.bauermann@gmail.com>,
"Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: Linux Kernel GDB tracepoint module 2010-8-30 release
Date: Sat, 04 Sep 2010 09:17:00 -0000 [thread overview]
Message-ID: <AANLkTimYgMotZBbGTvPGSzfo3jjZ_-TeXftVQ6bBzHrT@mail.gmail.com> (raw)
In-Reply-To: <1283590584.1685.39.camel@steven>
On Sat, Sep 4, 2010 at 16:56, Steven <mqyoung@gmail.com> wrote:
> On Sat, 2010-09-04 at 11:41 +0800, Hui Zhu wrote:
>> BTW, looks GCC and GDB don't want handle the optimization debug
>> trouble (all they want is rewrite the GCC in C++ :P).
>> So I think make linux kernel can close optimization is better idea, do
>> you know some way or some patch to do it?
>>
>
> Just disable CONFIG_CC_OPTIMIZE_FOR_SIZE and modify the Makefile of
> kernel:
> KBUILD_CFLAGS += -O2
> to
> KBUILD_CFLAGS += -O0
Cool, :)
I try just change the compile option of readdir.c to without -O2, it
works OK. I think maybe it's a GDB bug too.
Could you try the second issue with gdb 7.2?
BTW, I think I need add some words let all the KGTP user use gdb 7.2
with KGTP in howto. :)
Thanks for help me with this big issue. :)
Best,
Hui
>
> Sometime gcc will still optimize out some variables even I compile a
> program with -O0, so volatile is required sometimes.
>
> Thanks,
> Steven
>
>
next prev parent reply other threads:[~2010-09-04 9:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 7:07 Hui Zhu
2010-09-03 9:06 ` Steven
2010-09-03 14:06 ` Frank Ch. Eigler
2010-09-04 4:30 ` Hui Zhu
2010-09-04 5:11 ` Frank Ch. Eigler
2010-09-04 15:04 ` Hui Zhu
2010-09-04 16:35 ` Hui Zhu
2010-09-04 18:22 ` Frank Ch. Eigler
2010-09-04 3:42 ` Hui Zhu
2010-09-04 7:48 ` Hui Zhu
2010-09-04 9:01 ` Steven
2010-09-04 9:10 ` Hui Zhu
2010-09-04 8:39 ` Steven
[not found] ` <1283590584.1685.39.camel@steven>
2010-09-04 9:17 ` Hui Zhu [this message]
2010-09-04 9:26 ` Steven
2010-09-04 14:59 ` Hui Zhu
2010-09-04 16:02 ` Steven
2010-09-04 16:43 ` Hui Zhu
2010-09-04 16:48 ` Steven
2010-09-06 7:21 ` Hui Zhu
2010-09-06 7:51 ` Hui Zhu
2010-09-06 9:30 ` Log of Using KGTP Steven
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=AANLkTimYgMotZBbGTvPGSzfo3jjZ_-TeXftVQ6bBzHrT@mail.gmail.com \
--to=teawater@gmail.com \
--cc=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.khouzam@ericsson.com \
--cc=mqyoung@gmail.com \
--cc=msnyder@vmware.com \
--cc=thiago.bauermann@gmail.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