This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/11800] New: clarify stap -l "PROBE1,PROBE2,PROBE3" usage
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 8 Jul 2010 21:57:08 -0000
- Subject: [Bug translator/11800] New: clarify stap -l "PROBE1,PROBE2,PROBE3" usage
- Reply-to: sourceware-bugzilla at sourceware dot org
Due to awareness of an implementation artefact, some zany people
have started using stap -l/-L with a series of probe points rather
than one. A few may be creative enough to inject ! and ? punctuation
too. This may have happened to work because this happened to be
implemented by -p2-evaluation of 'probe $1 {}'.
Nay, says the man page. It promises satisfaction for just one
probe element.
Enter bug #11443 and commit 7972c9 et al. These broke some of the
former assumptions, and some of the testsuite/systemtap.examples
test_check predicates.
Too bad, say I. Let's document and assert that -l/-L takes only
a single solitary probe point. And change the test_check tests
to use individual stap -l PROBE1 && stap -l PROBE2 calls.
OR
Let's document and support the status quo ante, restoring these
crazy test_check widgets to their former inimitable glory.
--
Summary: clarify stap -l "PROBE1,PROBE2,PROBE3" usage
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: fche at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=11800
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.