public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: jistone@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-96-g4bf09a2
Date: Fri, 09 Mar 2012 06:50:00 -0000	[thread overview]
Message-ID: <20120309064959.10380.qmail@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "systemtap: system-wide probe/trace tool".

The branch, master has been updated
       via  4bf09a21457027eb511bb16a9355d6e17a93ae5f (commit)
       via  77c59b0d311c786c6a0cff2b35f6436fbe349ba0 (commit)
       via  dc53a28abd94706dc30cc063d2700eb3deb3c5f0 (commit)
       via  05fb3e0c90d5175acfca9cee7a6983b0c9b62f91 (commit)
      from  ebbfed0c51bade7cd4f92d7c754156a9f09fc4f9 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 4bf09a21457027eb511bb16a9355d6e17a93ae5f
Merge: ebbfed0 77c59b0
Author: Josh Stone <jistone@redhat.com>
Date:   Thu Mar 8 16:53:38 2012 -0800

    Merge branch 'sysroot'
    
    Conflicts:
    	cmdline.cxx
    	cmdline.h
    	session.cxx
    (Reconciled with commit 372c6458, "Long options rework.")

commit 77c59b0d311c786c6a0cff2b35f6436fbe349ba0
Author: Wade Farnsworth <wade_farnsworth@mentor.com>
Date:   Thu Mar 8 07:51:00 2012 -0700

    PR12331: Add testcase for --sysroot and --sysenv
    
    Signed-off-by: Wade Farnsworth <wade_farnsworth@mentor.com>

commit dc53a28abd94706dc30cc063d2700eb3deb3c5f0
Author: Wade Farnsworth <wade_farnsworth@mentor.com>
Date:   Thu Mar 8 07:49:58 2012 -0700

    PR12331: Document --sysroot and --sysenv
    
    Update stap.1 and NEWS to document the new options.

commit 05fb3e0c90d5175acfca9cee7a6983b0c9b62f91
Author: Wade Farnsworth <wade_farnsworth@mentor.com>
Date:   Thu Mar 8 07:49:04 2012 -0700

    PR12331: Introduce stap options --sysroot and --sysenv
    
    This adds new command-line options to facilitate different file locations at
    compile-time versus run-time when generating stap kernel modules for a remote
    system:
    
    1. --sysroot=DIR
       Specifies a separate filesystem for the remote system on the local
       system.  The following stap functionalities will make use of this:
    
       a. When compiling process and library probes with a remote filesystem path
          (e.g. process("/bin/foo") with --sysroot=/bar/baz).  In this case symbols
          will be taken from the local filesystem (/bar/baz/bin/foo), but the
          resulting .ko will still contain paths on the remote filesystem
          (/bin/foo).
    
       b. When passing a kernel release with -r (not a full path), the kernel
          build directory will be expected in the sysroot.
    
       c. When DWARF debug info is contained in a separate file from the
          executable, the sysroot is used to find the debug info files.
    
       d. All calls to find_executable() search the path passed in the
          argument env_path relative to the sysroot.  For example if
          PATH=/bin/foo, and --sysroot=/bar/baz is provided, then
          find_executable() called with env_path == "PATH" will search
          /bar/baz/bin/foo.
    
       e. stap attempts to detect if a path in a probe would be outside of the
          sysroot and errors appropriately.  This situation may occur, for
          example, if the path contains several ".." directories.
    
    2. --sysenv=VAR=VALUE
       Specifies a different environment variable for the remote system as opposed
       to the local one, and that the value on the remote system should be used.
       Currently only valid env_path arguments to find_executable() are handled
       (i.e. PATH, LD_LIBRARY_PATH).  If --sysroot is provided and --sysenv
       is omitted, then the local environment relative to the sysroot will
       be used.
    
    These options are disabled for systemtap clients.
    
    Signed-off-by: Wade Farnsworth <wade_farnsworth@mentor.com>

-----------------------------------------------------------------------

Summary of changes:
 cmdline.cxx                                 |    2 +
 cmdline.h                                   |    4 +-
 dwflpp.cxx                                  |    4 +-
 hash.cxx                                    |    3 +-
 main.cxx                                    |    9 ++++
 session.cxx                                 |   59 ++++++++++++++++++++++++
 session.h                                   |    3 +
 setupdwfl.cxx                               |   37 +++++++++++++--
 setupdwfl.h                                 |    1 +
 stap.1                                      |   13 +++++
 tapset-itrace.cxx                           |    7 ++-
 tapset-utrace.cxx                           |    7 ++-
 tapsets.cxx                                 |   66 ++++++++++++++++++---------
 tapsets.h                                   |    2 +
 testsuite/systemtap.base/sysroot_sysenv.exp |   15 ++++++
 testsuite/systemtap.base/sysroot_sysenv.stp |    3 +
 translate.cxx                               |    4 +-
 util.cxx                                    |   27 +++++++++---
 util.h                                      |    3 +
 19 files changed, 225 insertions(+), 44 deletions(-)
 create mode 100644 testsuite/systemtap.base/sysroot_sysenv.exp
 create mode 100644 testsuite/systemtap.base/sysroot_sysenv.stp


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2012-03-09  6:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20120309064959.10380.qmail@sourceware.org \
    --to=jistone@sourceware.org \
    --cc=systemtap-cvs@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).