From: William Cohen <wcohen@redhat.com>
To: David Smith <dsmith@redhat.com>,
Systemtap List <systemtap@sourceware.org>,
pcp <pcp@oss.sgi.com>
Subject: Re: [pcp] systemtap/pcp integration
Date: Mon, 21 Jul 2014 15:54:00 -0000 [thread overview]
Message-ID: <53CD37C2.1060705@redhat.com> (raw)
In-Reply-To: <53CD352E.8030101@redhat.com>
On 07/21/2014 11:43 AM, David Smith wrote:
> On 07/18/2014 04:10 PM, William Cohen wrote:
>> Hi David,
>>
>> I was able to get this to work on RHEL 7. However, on fedora20 the mmvdump
>> gets a sigsegv in the dump() function.
>
> Thanks for the bug report. I believe I just fixed this one, so after
> updating let me know if it doesn't work for you.
>
Hi David,
That fix made fedora 20 happy. In one window did:
$ ./systemtap_write/install/bin/stap mmv.stp
instances: 0, 1
indom: 0
metrics: 0, 1, 2
In another ran the mmvdump from pcp:
$ ./mmvdump /proc/systemtap/stap_cb2f18a783870e1474713324d01a25f_25939/mmv
MMV file = /proc/systemtap/stap_cb2f18a783870e1474713324d01a25f_25939/mmv
Version = 1
Generated = 769479
TOC count = 5
Cluster = 42
Process = 0
Flags = 0x0
TOC[0]: offset 40, indoms offset 1848 (1 entries)
[1/1848] 2 instances, starting at offset 152
shorttext=We can be heroes
helptext=Set of instances from zero to hero
TOC[1]: offset 56, instances offset 152 (2 entries)
[1/152] instance = [0 or "zero"]
[1/232] instance = [1 or "hero"]
TOC[2]: toc offset 72, metrics offset 1880 (3 entries)
[1/1880] counter
type=64-bit int (0x2), sem=counter (0x1), pad=0x0
units=count
(no indom)
shorttext=Example counter metric
helptext=Yep, a test counter metric
[2/1984] instant
type=64-bit int (0x2), sem=instant (0x3), pad=0x0
units=
(no indom)
shorttext=Example instant metric
helptext=Yep, a test instantaneous metric
[3/2088] indom
type=64-bit int (0x2), sem=discrete (0x4), pad=0x0
units=
indom=1
(no shorttext)
(no helptext)
TOC[3]: offset 88, values offset 2192 (4 entries)
[1/2192] counter = 0
[2/2224] instant = 325
[3/2256] indom[0 or "zero"] = 0
[3/2288] indom[0 or "zero"] = 0
TOC[4]: offset 104, string offset 312 (6 entries)
[1/312] We can be heroes
[2/568] Set of instances from zero to hero
[3/824] Example counter metric
[4/1080] Yep, a test counter metric
[5/1336] Example instant metric
[6/1592] Yep, a test instantaneous metric
-Will
next prev parent reply other threads:[~2014-07-21 15:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 21:14 David Smith
2014-07-18 15:49 ` Frank Ch. Eigler
2014-07-18 17:02 ` David Smith
2014-07-18 18:27 ` Frank Ch. Eigler
2014-07-22 14:25 ` David Smith
2014-07-22 15:21 ` Frank Ch. Eigler
2014-07-22 21:02 ` David Smith
2014-07-18 21:10 ` [pcp] " William Cohen
2014-07-21 15:43 ` David Smith
2014-07-21 15:54 ` William Cohen [this message]
2014-07-22 1:32 ` Nathan Scott
2014-07-22 2:57 ` Frank Ch. Eigler
2014-07-22 14:50 ` [pcp] " David Smith
2014-07-23 10:29 ` Nathan Scott
2014-07-23 14:42 ` Frank Ch. Eigler
2014-07-24 7:40 ` Nathan Scott
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=53CD37C2.1060705@redhat.com \
--to=wcohen@redhat.com \
--cc=dsmith@redhat.com \
--cc=pcp@oss.sgi.com \
--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).