From: fche@redhat.com (Frank Ch. Eigler)
To: "Hassan Radwan" <HassanR@avi.com>
Cc: <systemtap@sourceware.org>
Subject: Re: Skipped Probes for userspace constructors, Why?
Date: Sun, 23 Nov 2008 17:07:00 -0000 [thread overview]
Message-ID: <y0m3ahi9xsa.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <2131D39DDCC1CF4EBBDBA9994701D921B5974F@hicksville.avi.com> (Hassan Radwan's message of "Mon, 10 Nov 2008 14:57:11 -0500")
"Hassan Radwan" <HassanR@avi.com> writes:
> [...]
> I have a simple script written to try and understand when the
> constructor is called for the classes in an application. [...]
> probe process("a.out").function("FooConstructor") [...]
> [...]
> $ sudo stap foo.stp -c a.out
> WARNING: Number of errors: 0, skipped probes: 195
If able, build yourself a new copy of systemtap out of the git tree,
and run your test with the "-t" (timing) flag. You should get more
detailed counts about what skipped. I believe there was also a bug
fixed related to the new MAXUPROBES configurable, which may have
enabled a much smaller number of uprobes than intended.
- FChE
prev parent reply other threads:[~2008-11-23 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 19:58 Hassan Radwan
2008-11-23 17:07 ` 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=y0m3ahi9xsa.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=HassanR@avi.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).