From: "srinivasa at in dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/4793] New: duplicate probe aliases for sys_quotactl, sys_request_key on ppc64.
Date: Mon, 16 Jul 2007 09:02:00 -0000 [thread overview]
Message-ID: <20070716083137.4793.srinivasa@in.ibm.com> (raw)
While executing this week's systemtap snapshot(20070714) test, I encountered
test failures with following error message.
quotactl and request_key systemcall probe aliases are defined in syscalls.stp
file, under separate arch directory(like
tapset/ppc64/syscalls.stp,tapset/i686/syscalls.stp etc)
This week these systemcall aliases are moved to arch independent syscalls2.stp
file(tapset/syscalls2.stp) but corresponding entry in arch file has not been
removed for ppc64. Hence this bug.
==================================================================
Pass 1: parsed user script and 55 library script(s) in 1220usr/10sys/1352real ms.^M
Pass 1: parsed user script and 55 library script(s) in 1220usr/10sys/1352real
ms.^M
semantic error: duplicate probe point pattern while registering probe alias
syscall.quotactl = kernel.function("sys_quotactl")^M
semantic error: duplicate probe point pattern while registering probe alias
syscall.quotactl = kernel.function("sys_quotactl")^M
semantic error: duplicate probe point pattern while registering probe alias
syscall.quotactl.return = kernel.function("sys_quotactl").return^M
semantic error: duplicate probe point pattern while
registering probe alias syscall.quotactl.return
= kernel.function("sys_quotactl").return^M
semantic error: duplicate probe point pattern while
registering probe alias syscall.request_key = k
ernel.function("sys_request_key")?^M
semantic error: duplicate probe point pattern while registering probe alias
syscall.request_key = kernel.function("sys_request_key")?^M
semantic error: duplicate probe point pattern while registering probe alias
syscall.request_key.return = kernel.function("sys_request_key").return?^M
semantic error: duplicate probe point pattern while
registering probe alias syscall.request_key.ret
urn = kernel.function("sys_request_key").return?^M
=========================================================
--
Summary: duplicate probe aliases for sys_quotactl,
sys_request_key on ppc64.
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: srinivasa at in dot ibm dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=4793
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-07-16 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 9:02 srinivasa at in dot ibm dot com [this message]
2007-07-31 14:36 ` [Bug tapsets/4793] " srinivasa at in dot ibm dot com
2007-08-02 16:44 ` 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=20070716083137.4793.srinivasa@in.ibm.com \
--to=sourceware-bugzilla@sourceware.org \
--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).