From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/13501] New: Some arguments for 'stap -L "*, *.*, *.*.*" ' probe points not found
Date: Wed, 14 Dec 2011 22:01:00 -0000 [thread overview]
Message-ID: <bug-13501-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13501
Bug #: 13501
Summary: Some arguments for 'stap -L "*, *.*, *.*.*" ' probe
points not found
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap@sourceware.org
ReportedBy: wcohen@redhat.com
Classification: Unclassified
Created attachment 6110
--> http://sourceware.org/bugzilla/attachment.cgi?id=6110
stderr output listing problems with RHEL6 run of stap -L "*, *.*, *.*.*"
One would like to get an exhaustive list of probe points with:
stap -L "*, *.*, *.*.*"
However, on x86-64 RHEL 6.2 with systemtap 1.6 get a number of warnings about
arguments not being available. Also get similar warnings on x86-64 Fedora
rawhide.
On RHEL6:
kernel-2.6.32-220.el6.x86_64
systemtap-1.6-4.el6.x86_64
On Fedora rawhide:
kernel-3.2.0-0.rc5.git1.1.fc17.x86_64
systemtap-1.6-1.fc16.x86_64
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-12-14 21:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 22:01 wcohen at redhat dot com [this message]
2011-12-15 11:35 ` [Bug tapsets/13501] " wcohen at redhat dot com
2011-12-15 15:32 ` dsmith at redhat dot com
2011-12-15 15:53 ` dsmith at redhat dot com
2011-12-15 16:14 ` dsmith at redhat dot com
2011-12-15 18:34 ` dsmith at redhat dot com
2011-12-15 19:14 ` dsmith at redhat dot com
2011-12-15 19:30 ` dsmith at redhat dot com
2011-12-16 17:42 ` dsmith at redhat dot com
2011-12-16 17:57 ` dsmith at redhat dot com
2011-12-17 1:08 ` dsmith at redhat dot com
2011-12-19 21:09 ` dsmith at redhat dot com
2017-05-08 20:31 ` fche at redhat dot com
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=bug-13501-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).