All of lore.kernel.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: Steven <mqyoung@gmail.com>
Cc: Hui Zhu <teawater@gmail.com>,
	"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 10:05:56 -0400	[thread overview]
Message-ID: <y0md3suzzuj.fsf@fche.csb> (raw)
In-Reply-To: <1283504768.2100.43.camel@steven> (mqyoung@gmail.com's message of "Fri, 03 Sep 2010 17:06:08 +0800")


Steven <mqyoung@gmail.com> writes:

> [...]
>         (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

By the way, the systemtap equivalent would be:

#! /usr/bin/stap -g
probe kernel.function("vfs_readdir") {
      println(%{ jiffies_64 %})
      println($file$)
}


> 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


#! /usr/bin/stap
probe kernel.statement("*@fs/readdir.c:29") {
      println($res)
}


- FChE

  reply	other threads:[~2010-09-03 14: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
2010-09-03 14:05   ` Frank Ch. Eigler [this message]
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=y0md3suzzuj.fsf@fche.csb \
    --to=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.