public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Kevin Jia" <jiaminghao@gmail.com>
To: "William Cohen" <wcohen@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: Urgent Help!
Date: Sun, 05 Mar 2006 04:35:00 -0000	[thread overview]
Message-ID: <30c154100603042035odd5c4cavaf03c628060b0dd6@mail.gmail.com> (raw)
In-Reply-To: <4409AEA3.2050102@redhat.com>

ok, thank you very much.

On 3/5/06, William Cohen <wcohen@redhat.com> wrote:
> Kevin Jia wrote:
> > I'm a systemtap beginner, so I need more source code of test and the
> > manual of systemtap instruction. You can send me some or tell me the
> > website. Thank you very much!
>
> Sorry there isn't a nice document document on the website describing how
> to build/run tests. There are runtime tests that can be checked out with:
>
> cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/systemtap login
> {enter "anoncvs" as the password}
> cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/systemtap co tests
>
> There are a number of tests in the subdirectories of tests/testsuite.
> Just do a "find -path "*.stp" and you will see them. The tests are run
> with "runtest --tool=systemtap" in the tests/testsuite directory.
>
> There is a script, tests/tools/stap_testing, that automatically pulls
> down the current cvs snapshots and build things in your home directory.
> It expects to have the source code for elfutils-0.119 around in
> rh-rpm/BUILD. It should give you some insight on how to run and build
> things. However, you might want to stick to using the already built
> SystemTap RPMs available for Fedora Core.
>
> -Will
>

      reply	other threads:[~2006-03-05  4:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-04  2:59 Kevin Jia
2006-03-04 15:13 ` William Cohen
2006-03-05  4:35   ` Kevin Jia [this message]

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=30c154100603042035odd5c4cavaf03c628060b0dd6@mail.gmail.com \
    --to=jiaminghao@gmail.com \
    --cc=systemtap@sourceware.org \
    --cc=wcohen@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).