public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "guanglei at cn dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug documentation/2334] New: -vv & -vvv option of stap
Date: Tue, 14 Feb 2006 06:56:00 -0000	[thread overview]
Message-ID: <20060214065638.2334.guanglei@cn.ibm.com> (raw)

the -vv option of stap will print much more info than -v option, and the -vvv
will give all the verbose info. But stap doesn't document them.

And we should also change the message given by stap if an error occurs during
Pass 1 to Pass 4. One of them is the compiling error:

[root@localhost stap-trace--unstable--0.1]# stap lgl.stp  -I tapsets/ 
Pass 4: compilation failed.  Try again with '-v' (verbose) option.

if you use -v option, in fact you won't get any kof the compiling process. So it
should change to:
Pass 4: compilation failed.  Try again with '-vv'or '-vvv' option.

-- 
           Summary: -vv & -vvv option of stap
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: documentation
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: guanglei at cn dot ibm dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=2334

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

             reply	other threads:[~2006-02-14  6:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-14  6:56 guanglei at cn dot ibm dot com [this message]
2006-02-14 12:23 ` [Bug documentation/2334] " fche at redhat dot com
2006-02-23 22:36 ` fche 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=20060214065638.2334.guanglei@cn.ibm.com \
    --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).