From: "craig.ringer at 2ndquadrant dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/26254] [PATCH] Syntax error in sssd_functions.stp at METHOD_SENTINEL
Date: Fri, 17 Jul 2020 02:47:25 +0000 [thread overview]
Message-ID: <bug-26254-6586-TsuIlqH3Uw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26254-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26254
Craig Ringer <craig.ringer at 2ndquadrant dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
URL| |https://github.com/SSSD/sss
| |d/commit/66029529fa0f0e2d16
| |999f22294822deeec5f60b
Resolution|--- |INVALID
--- Comment #1 from Craig Ringer <craig.ringer at 2ndquadrant dot com> ---
Fixed by sssd commit
https://github.com/SSSD/sssd/commit/66029529fa0f0e2d16999f22294822deeec5f60b
Apply that patch if you hit this error.
Proposal: in systemtap errors, identify built-in tapsets vs externally provided
tapsets. Perhaps a pragma or similar that allows tapsets to be labeled with
their originating package? It might be obvious that this is part of sssd, but
only if you know what sssd is, and that it's installed...
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-07-17 2:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 2:45 [Bug tapsets/26254] New: " craig.ringer at 2ndquadrant dot com
2020-07-17 2:47 ` craig.ringer at 2ndquadrant dot com [this message]
2020-07-17 15:10 ` [Bug tapsets/26254] " 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-TsuIlqH3Uw@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).