From: "craig.ringer at 2ndquadrant dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/26254] New: [PATCH] Syntax error in sssd_functions.stp at METHOD_SENTINEL
Date: Fri, 17 Jul 2020 02:45:34 +0000 [thread overview]
Message-ID: <bug-26254-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26254
Bug ID: 26254
Summary: [PATCH] Syntax error in sssd_functions.stp at
METHOD_SENTINEL
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: craig.ringer at 2ndquadrant dot com
Target Milestone: ---
I see the following complaint on even trivial probes on Fedora 32:
parse error: expected 'probe', 'global', 'private', 'function', or '%{'
saw: identifier 'METHOD_SENTINEL' at
/usr/share/systemtap/tapset/sssd_functions.stp:10:34
source: METHOD_RESOLVER_HANDLER=9 METHOD_SENTINEL=10
^
This turns out to be in an externally supplied tapset:
$ rpm -qf /usr/share/systemtap/tapset/sssd_functions.stp
sssd-common-2.3.0-1.fc32.x86_64
but I'm opening an issue here to make the problem searchable, since I had
started a bug before I realised it wasn't part of systemtap itself. It's fixed
in upstream sssd by
https://github.com/SSSD/sssd/blob/master/src/systemtap/sssd_functions.stp .
The cause is a missing comma.
My versions:
$ rpm -q --qf '%{name}-%{version}-%{release}\n' gcc gcc
fedora-release-workstation
gcc-10.1.1-1.fc32
gcc-10.1.1-1.fc32
fedora-release-workstation-32-3
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-07-17 2:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 2:45 craig.ringer at 2ndquadrant dot com [this message]
2020-07-17 2:47 ` [Bug tapsets/26254] " craig.ringer at 2ndquadrant dot com
2020-07-17 15:10 ` wcohen 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-26254-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).