From: fche@redhat.com (Frank Ch. Eigler)
To: Huang jw <huangjiangwei@gmail.com>
Cc: Roland McGrath <roland@redhat.com>, systemtap@sourceware.org
Subject: Re: about probe libc
Date: Wed, 11 Aug 2010 15:03:00 -0000 [thread overview]
Message-ID: <y0mocd99oof.fsf@fche.csb> (raw)
In-Reply-To: <AANLkTinFF9wusngvLV8cfRGaY4_Fe24_VJVVXUm-SUti@mail.gmail.com> (Huang jw's message of "Tue, 10 Aug 2010 14:31:58 +0800")
Huang jw <huangjiangwei@gmail.com> writes:
> As you said, it's difficult to trace memcpy by systemtap because of
> inline or Macros. [...]
One more thing worth trying is probing the inlined instances within
the process binary (instead of just the copy in the libc.so), as
in
probe process("a.out").function("memcpy"),
process("/lib/libc.5.so").function("memcpy") {
log($$parms)
}
The former may catch the synthetic ones.
- FChE
prev parent reply other threads:[~2010-08-11 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 4:49 Huang jw
2010-08-10 5:27 ` Srikar Dronamraju
2010-08-10 5:43 ` Huang jw
2010-08-10 6:03 ` Roland McGrath
2010-08-10 6:00 ` Roland McGrath
2010-08-10 6:32 ` Huang jw
2010-08-11 15:03 ` Frank Ch. Eigler [this message]
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=y0mocd99oof.fsf@fche.csb \
--to=fche@redhat.com \
--cc=huangjiangwei@gmail.com \
--cc=roland@redhat.com \
--cc=systemtap@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).