From: David Smith <dsmith@redhat.com>
To: Wade Farnsworth <wade_farnsworth@mentor.com>
Cc: systemtap@sourceware.org
Subject: Re: Concurrent userspace probes targeting same location
Date: Thu, 05 Jul 2012 16:15:00 -0000 [thread overview]
Message-ID: <4FF5BD93.50805@redhat.com> (raw)
In-Reply-To: <4FF3661F.80100@mentor.com>
On 07/03/2012 04:37 PM, Wade Farnsworth wrote:
> David Smith wrote:
>> Running multiple return probes at the same location in the same script
>> should work.
I've duplicated your problem. This is quite odd, especially since both
probes are getting inserted at the exact same address (0x8x520), as
shown by the following "stap -p2" output:
# stap -p2 -d /bin/ls ../ls_malloc.stp -c ls | more
...
# probes
process("/lib64/libc-2.14.90.so").function("__libc_malloc@/usr/src/debug/glibc-2.14-394-g8f3b1ff/malloc/malloc.c:2913").return?
/* pc=.dynamic+0x82520 */ /* <-
process("/bin/ls").library("libc.so.6").function("malloc").return? =
process("/bin/ls").library("/lib64/libc-2.14.90.so").function("malloc").return?
<- process("/bin/ls").library("libc.so.6").function("malloc").return */
process("/lib64/libc-2.14.90.so").function("__libc_malloc@/usr/src/debug/glibc-2.14-394-g8f3b1ff/malloc/malloc.c:2913").return?
/* pc=.dynamic+0x82520 */ /* <-
process("/bin/ls").library("libc.so.6").function("malloc").return? =
process("/bin/ls").library("/lib64/libc-2.14.90.so").function("malloc").return?
<- process("/bin/ls").library("libc.so.6").function("malloc").return */
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
next prev parent reply other threads:[~2012-07-05 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 20:07 Wade Farnsworth
2012-07-03 21:31 ` David Smith
2012-07-03 21:38 ` Wade Farnsworth
2012-07-05 16:15 ` David Smith [this message]
2012-07-10 13:32 ` Frank Ch. Eigler
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=4FF5BD93.50805@redhat.com \
--to=dsmith@redhat.com \
--cc=systemtap@sourceware.org \
--cc=wade_farnsworth@mentor.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).