All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Steven <mqyoung@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: Sat, 4 Sep 2010 01:11:38 -0400	[thread overview]
Message-ID: <20100904051138.GC10118@redhat.com> (raw)
In-Reply-To: <AANLkTi=V13SpXeMzmnCWvh-ooAgnVP8kA5UsBsm89YDr@mail.gmail.com>

Hi -

On Sat, Sep 04, 2010 at 12:29:56PM +0800, Hui Zhu wrote:

> [...] Could you talk about how it do call stack dump like following?
> (gdb) trace vfs_readdir
> Tracepoint 1 at 0xffffffff8113f7fc: file
> /home/teawater/kernel/linux-2.6/fs/readdir.c, line 24.
> (gdb) actions
> >collect *(unsigned char *)$rsp@512

probe kernel.function("vfs_readdir") {
   // if you want the whole kernel-side backtrace, dwarf-unwound
   print_backtrace() 
   // or else just hex-dump a region
   printf("%*M\n", 512, register("rsp"))
}


> BTW, I was not find out which ARCH of the systemtap support in its
> website?  It support all the arch that kprobe support?

Yes, basically, though it's mostly tested on RHELy platforms (x86,
powerpc, s390, ia64).

- FChE

  reply	other threads:[~2010-09-04  5:11 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
2010-09-04  4:29     ` Hui Zhu
2010-09-04  5:11       ` Frank Ch. Eigler [this message]
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=20100904051138.GC10118@redhat.com \
    --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.