From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug documentation/11059] No dtrace script documentation
Date: Mon, 07 Dec 2009 06:00:00 -0000 [thread overview]
Message-ID: <20091207060046.20567.qmail@sourceware.org> (raw)
In-Reply-To: <20091206205410.11059.mjw@redhat.com>
------- Additional Comments From mjw at redhat dot com 2009-12-07 06:00 -------
It is actually not that bad, there is dtrace --help, which gives:
Usage /usr/local/bin/dtrace [--help] [-h | -G] -s File.d [-o File]
Where -h builds a systemtap header file from the .d file
-o specifies an explicit output file name,
The default for -G is file.o and -h is file.h
-s specifies the name of the .d input file
-G builds a stub file.o from file.d,
which is required by some packages that use dtrace.
Still would be nice to have an actual man page though.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11059
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-12-07 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 20:54 [Bug documentation/11059] New: " mjw at redhat dot com
2009-12-07 6:00 ` mjw at redhat dot com [this message]
2010-01-18 20:18 ` [Bug documentation/11059] " fche at redhat dot com
2010-01-19 19:50 ` 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=20091207060046.20567.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).