[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimYgMotZBbGTvPGSzfo3jjZ_-TeXftVQ6bBzHrT@mail.gmail.com>
Date: Sat, 4 Sep 2010 17:17:27 +0800
From: Hui Zhu <teawater@...il.com>
To: Steven <mqyoung@...il.com>
Cc: "gdb@...rceware.org" <gdb@...rceware.org>,
linux-kernel@...r.kernel.org, Michael Snyder <msnyder@...are.com>,
Marc Khouzam <marc.khouzam@...csson.com>,
Thiago Jung Bauermann <thiago.bauermann@...il.com>,
"Frank Ch. Eigler" <fche@...hat.com>
Subject: Re: Linux Kernel GDB tracepoint module 2010-8-30 release
On Sat, Sep 4, 2010 at 16:56, Steven <mqyoung@...il.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
>
>
--
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/
Powered by blists - more mailing lists