From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/20307] tapset/linux/rpc.stp error
Date: Tue, 28 Jun 2016 15:56:00 -0000 [thread overview]
Message-ID: <bug-20307-6586-iS6JQvRv5J@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20307-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20307
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|tapset/linux/rpc.stp error |tapset/linux/rpc.stp error
|(possible because of |
|'private' keyword) |
--- Comment #1 from David Smith <dsmith at redhat dot com> ---
This happened to me on RHEL7.2 ppc64. It does not happen on rawhide x86_64.
This would seem to indicate that 'private' isn't the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-06-28 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 14:05 [Bug translator/20307] New: tapset/linux/rpc.stp error (possible because of 'private' keyword) dsmith at redhat dot com
2016-06-28 15:56 ` dsmith at redhat dot com [this message]
2016-06-28 18:13 ` [Bug translator/20307] tapset/linux/rpc.stp error dsmith at redhat dot com
2016-06-29 18:33 ` dsmith at redhat dot com
2016-06-29 18:34 ` [Bug translator/20307] 'private' on tapset global arrays causes errors dsmith at redhat dot com
2016-06-29 20:44 ` fche at redhat dot com
2016-06-30 15:11 ` mcermak at redhat dot com
2016-06-30 16:11 ` fche at redhat dot com
2016-07-01 7:31 ` mcermak 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-20307-6586-iS6JQvRv5J@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).