From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/23605] Intermittent errors when running a simplest stap script against a simplest target program
Date: Tue, 04 Sep 2018 19:44:00 -0000 [thread overview]
Message-ID: <bug-23605-6586-NaSj5ZzlNC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23605-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23605
--- Comment #1 from agentzh <agentzh at gmail dot com> ---
I'm using the dyninst-devel package from Fedora 27's official yum repo:
```
$ dnf info dyninst-devel
Fedora 27 - x86_64 - Updates
3.0 MB/s | 26 MB 00:08
Fedora 27 - x86_64
6.2 MB/s | 58 MB 00:09
OpenResty Proprietary Repository
34 MB/s | 92 kB 00:00
Installed Packages
Name : dyninst-devel
Version : 9.3.2
Release : 7.fc27
Arch : x86_64
Size : 1.2 M
Source : dyninst-9.3.2-7.fc27.src.rpm
Repo : @System
From repo : updates
Summary : Header files for the compiling programs with Dyninst
URL : http://www.dyninst.org
License : LGPLv2+
Description : dyninst-devel includes the C header files that specify the
Dyninst user-space
: libraries and interfaces. This is required for rebuilding any
program
: that uses Dyninst.
```
Extra verbosity is a bit tricky since it is hard to reproduce and only
reproducible when running my test suite.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-09-04 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 18:52 [Bug dyninst/23605] New: " agentzh at gmail dot com
2018-09-04 19:44 ` agentzh at gmail dot com [this message]
2018-09-04 20:32 ` [Bug dyninst/23605] " agentzh at gmail dot com
2018-09-04 21:14 ` agentzh at gmail dot com
2019-04-05 15:25 ` scox 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-23605-6586-NaSj5ZzlNC@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).