public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven <mqyoung@gmail.com>
To: Hui Zhu <teawater@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>
Subject: Re: Linux Kernel GDB tracepoint module 2010-8-30 release
Date: Fri, 03 Sep 2010 17:06:08 +0800	[thread overview]
Message-ID: <1283504768.2100.43.camel@steven> (raw)
In-Reply-To: <AANLkTimjO7sBzR55XkPB7dmZvxXqc8PS4UDsgptXVt90@mail.gmail.com>

Dear Hui,

I encountered two issue when I use your GTP.

1) Following your HOWTO, I collect the two variables jiffies_64(global),
*file(argument), the result are as following, where you may see
jiffies_64 = 4298520928, that's OK, but the members of *file are all 0.
What's the problem? Thank you very much!
        -------------------------------------------------------------------
        (gdb) trace vfs_readdir 
        Tracepoint 3 at 0xc1175690: file fs/readdir.c, line 23.
        (gdb) actions
        Enter actions for tracepoint 3, one per line.
        End with a line saying just "end".
        > collect jiffies_64
        > collect *file
        > end
        (gdb) tstart
        (gdb) tstop
        (gdb) tfind
        #0  0xc1175691 i (file=0x0, filler=0, buf=0x0) at
        fs/readdir.c:23
        23      {
        (gdb) p jiffies_64
        $7 = 4298520928
        (gdb) p *file
        $8 = {f_u = {fu_list = {next = 0x0, prev = 0x0}, fu_rcuhead =
        {next = 0x0, func = 0}}, f_path = {mnt = 0x0, dentry = 0x0},
        f_op = 0x0, f_lock = {{ rlock = {raw_lock = {slock = 0}}}},
        f_count = {counter = 0}, f_flags = 0, f_mode = 0, f_pos = 0,
        f_owner = {lock = {raw_lock = { lock = 0}}, pid = 0x0, pid_type
        = PIDTYPE_PID, uid = 0, euid = 0, signum = 0}, f_cred = 0x0,
        f_ra = {stra_pages = 00, f_security = 0x0, private_data = 0x0,
        f_ep_links = {next = 0x0, prev = 0x0}, f_mapping = 0x0}
        -------------------------------------------------------------------


2) I can not collect local variable, despite I rebuild the kernel with
-O0 optimization option. what is the problem? Many thanks
        -------------------------------------------------------------------
        (gdb) trace fs/readdir.c:29
        Tracepoint 2 at 0xc11756ca: file fs/readdir.c, line 29.
        (gdb) actions 
        Enter actions for tracepoint 2, one per line.
        End with a line saying just "end".
        > collect res
        > end
        (gdb) tstart
        res: don't know symbol class 20
        -------------------------------------------------------------------
        
        Code fragment of readdir.c
        -------------------------------------------------------------------
         22 int vfs_readdir(struct file *file, filldir_t filler, void
        *buf)
         23 {
         24         struct inode *inode = file->f_path.dentry->d_inode;
         25         int res = -ENOTDIR;
         26         if (!file->f_op || !file->f_op->readdir)
         27                 goto out;
         28 
         29         res = security_file_permission(file, MAY_READ);
         30         if (res)
         31                 goto out;
        -------------------------------------------------------------------

Best Regards,
Steven


On Mon, 2010-08-30 at 15:00 +0800, Hui Zhu wrote:
> http://kgtp.googlecode.com/files/kgtp_20100830.tar.bz2
> or
> svn co https://kgtp.googlecode.com/svn/tags/20100830
> to get it.
> 
> Fix bug in ref16, ref32, ref64 in issue
> https://code.google.com/p/kgtp/issues/detail?id=2
> Fix bug that disable some tracepoint will make "tstart" get error.
> 
> Support qtstatus. Then KGTP support GDB command "tstatus".
> Add support for "make install" and "make uninstall".
> Add support for qtro. Fix a bug about GTP_GDBRSP_REG_SIZE.
> 
> Change gtp_list make it more efficient.
> 
> Please goto http://code.google.com/p/kgtp/wiki/HOWTO to get more info
> about how to use KGTP.



  reply	other threads:[~2010-09-03  9:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30  7:00 Linux Kernel GDB tracepoint module 2010-8-30 release Hui Zhu
2010-09-03  9:06 ` Steven [this message]
2010-09-03 14:05   ` Frank Ch. Eigler
2010-09-04  4:29     ` Hui Zhu
2010-09-04  5:11       ` Frank Ch. Eigler
2010-09-04 15:04         ` Hui Zhu
2010-09-04 16:34     ` Hui Zhu
2010-09-04 18:22       ` Frank Ch. Eigler
2010-09-04  3:41   ` Hui Zhu
2010-09-04  7:47     ` 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:58           ` Hui Zhu
2010-09-04 16:01             ` Steven
2010-09-04 16:42               ` Hui Zhu
2010-09-04 16:47                 ` Steven
2010-09-06  7:21                   ` Hui Zhu
2010-09-06  7:50                     ` 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=1283504768.2100.43.camel@steven \
    --to=mqyoung@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.khouzam@ericsson.com \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.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