From: "mysecondaccountabc at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/22582] SystemTap 3.2 stap script compilation error opt
Date: Mon, 11 Dec 2017 22:16:00 -0000 [thread overview]
Message-ID: <bug-22582-6586-NivA4xnNXD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22582-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22582
--- Comment #2 from Gustavo Moreira <mysecondaccountabc at gmail dot com> ---
Created attachment 10680
--> https://sourceware.org/bugzilla/attachment.cgi?id=10680&action=edit
stap temporary files
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-12-11 22:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 8:13 [Bug runtime/22582] New: " mysecondaccountabc at gmail dot com
2017-12-11 14:18 ` [Bug runtime/22582] " dsmith at redhat dot com
2017-12-11 22:16 ` mysecondaccountabc at gmail dot com [this message]
2017-12-11 22:21 ` mysecondaccountabc at gmail dot com
2017-12-11 22:27 ` mysecondaccountabc at gmail dot com
2017-12-12 15:04 ` dsmith at redhat dot com
2017-12-13 5:21 ` mysecondaccountabc at gmail dot com
2017-12-13 18:47 ` dsmith at redhat dot com
2024-01-18 1:57 ` 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-22582-6586-NivA4xnNXD@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).