From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/25177] stap --bpf -c does not work as specified
Date: Thu, 25 Feb 2021 20:32:58 +0000 [thread overview]
Message-ID: <bug-25177-6586-8PyG1MC8LI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25177-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25177
Serhei Makarov <me at serhei dot io> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Serhei Makarov <me at serhei dot io> ---
implemented as of 76d56671cb
Had to link in start_cmd() from staprun to avoid too much redundant code.
(That raises the possibility of also using dbug(), err(), warn() in stapbpf
with their better formatting and colorization. But not relevant to this bug.)
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2021-02-25 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 15:58 [Bug bpf/25177] New: " me at serhei dot io
2021-02-04 16:31 ` [Bug bpf/25177] " wcohen at redhat dot com
2021-02-25 20:32 ` me at serhei dot io [this message]
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-25177-6586-8PyG1MC8LI@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).