From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/13155] conflicting tracepoint headers block stap -l / stap -p4
Date: Fri, 30 Sep 2011 20:46:00 -0000 [thread overview]
Message-ID: <bug-13155-6586-tmXnF3PBcj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13155-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13155
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
Summary|tracepoints probe breakage |conflicting tracepoint
| |headers block stap -l /
| |stap -p4
--- Comment #7 from Frank Ch. Eigler <fche at redhat dot com> 2011-09-30 20:46:17 UTC ---
Unfortunately attachment #1 is enough only to make the stap -l work.
Several tracepoint headers still conflict, which makes scripts like
probe kernel.trace("*") {}
break during pass 4 due to inter-header conflicts.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-09-30 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 10:43 [Bug translator/13155] New: tracepoints probe breakage phan at redhat dot com
2011-09-07 7:28 ` [Bug translator/13155] " phan at redhat dot com
2011-09-07 10:49 ` mjw at redhat dot com
2011-09-08 5:43 ` phan at redhat dot com
2011-09-12 10:43 ` mjw at redhat dot com
2011-09-12 10:54 ` mjw at redhat dot com
2011-09-13 4:23 ` phan at redhat dot com
2011-09-30 20:46 ` fche at redhat dot com [this message]
2011-10-05 19:49 ` [Bug translator/13155] conflicting tracepoint headers block stap -l / stap -p4 jistone at redhat dot com
2011-10-05 20:47 ` 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-13155-6586-tmXnF3PBcj@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).