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 14:59:00 -0000 [thread overview]
Message-ID: <AANLkTim5_vf9Tg1g13HAmiO7zAjPzR6QaJ3k2edQzkCv@mail.gmail.com> (raw)
In-Reply-To: <1283592366.1685.50.camel@steven>
On Sat, Sep 4, 2010 at 17:26, Steven <mqyoung@gmail.com> wrote:
> On Sat, 2010-09-04 at 17:17 +0800, Hui Zhu wrote:
>> 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?
>
> I have covered the two issues in the previous mail that I could collect
> both global variables and locals(-O0 kernel + gdb7.2):
>
> --------
> (gdb) trace vfs_readdir
> Tracepoint 3 at 0xc11756a0: file fs/readdir.c, line 24.
> (gdb) actions
> Enter actions for tracepoint 3, one per line.
> End with a line saying just "end".
> >collect *file
> >end
> (gdb) trace fs/readdir.c:29
> Tracepoint 4 at 0xc11756ca: file fs/readdir.c, line 29.
> (gdb) actions
> Enter actions for tracepoint 4, one per line.
> End with a line saying just "end".
> >collect res
> >end
> (gdb) tstart
> (gdb) tstop
> (gdb) tfind
> Found trace frame 0, tracepoint 3
> #0 0xc11756a1 in vfs_readdir (file=0xc7b2cf00, filler=0,
> buf=0x0)
> at fs/readdir.c:24
> 24 struct inode *inode =
> file->f_path.dentry->d_inode;
> (gdb) p *file
> $4 = {f_u = {fu_list = {next = 0xc6dca500, prev = 0xc7ade480},
> fu_rcuhead = {
> next = 0xc6dca500, func = 0xc7ade480}}, f_path = {mnt =
> 0xc6c05300,
> dentry = 0xc761d440}, f_op = 0xc1709a20, f_lock = {{rlock =
> {raw_lock = {
> slock = 0}}}}, f_count = {counter = 2}, f_flags =
> 624640,
> f_mode = 29, f_pos = 0, f_owner = {lock = {raw_lock = {lock =
> 16777216}},
> = 0start = 0, size = 0, async_size = 0,
> ra_pages = 32, mmap_miss = 0, prev_pos = -1}, f_version =
> 0,
> f_security = 0xc7b30120, private_data = 0x0, f_ep_links = {
> next = 0xc7b2cf74, prev = 0xc7b2cf74}, f_mapping =
> 0xc761c74c}
> (gdb) p res
> $5 = 0
> (gdb) tfind
> Found trace frame 1, tracepoint 4
> 0xc11756cb 29 res =
> security_file_permission(file, MAY_READ);
> (gdb) p res
> $6 = -20
> --------
>
>
>
Great. :)
Hui
next prev parent reply other threads:[~2010-09-04 14:59 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
2010-09-04 9:26 ` Steven
2010-09-04 14:59 ` Hui Zhu [this message]
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=AANLkTim5_vf9Tg1g13HAmiO7zAjPzR6QaJ3k2edQzkCv@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