From: William Cohen <wcohen@redhat.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: prompt script exiting
Date: Fri, 02 Dec 2005 20:08:00 -0000 [thread overview]
Message-ID: <4390A9A5.2090900@redhat.com> (raw)
When running the testsuite with the recent version of systemtap
(snapshot from this morning, 2005-12-02) I found that syscalls2.exp
would consistently fail. The the tests uses an exit() in the script when
a probe fires 100 times. The syscalls2.exp allows a little slop and the
probe to fire after the exit but before being removed. However, the
changes in how exit operates makes create a longer wait before scripts
actually exits. On the test runs I saw the probe fire 232, 200, 267, and
420 times on various machines, much more than the 150 times allowed in
the test.
Do we expect the script to exit promptly when the exit() is encountered
in the script? People taking measurements will want to know about this
because it could significantly affect the data their scripts collect.
For the time being we can just document this as how it behaves. It
should be fairly easy for users to have a predicate in their
instrumentation, so it is a pretty minor issue.
-Will
next reply other threads:[~2005-12-02 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 20:08 William Cohen [this message]
2005-12-12 11:35 Mao, Bibo
2005-12-12 15:26 ` Frank Ch. Eigler
2005-12-12 15:42 ` William Cohen
2005-12-12 15:49 ` Frank Ch. Eigler
2005-12-12 20:22 ` William Cohen
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=4390A9A5.2090900@redhat.com \
--to=wcohen@redhat.com \
--cc=systemtap@sources.redhat.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).