Jumpshot


Up: Visualizing Program Behavior Next: Configure Options Previous: Building and Using Jumpshot-3

Jumpshot is distributed with 2 script files, jumpshot.in (for use with JAVA 1.1.*) and jumpshot12.in (for use with JAVA 1.2.*), which are located in the jumpshot/build/unix/bin subdirectory. The purpose of these script files is to set the CLASSPATH variable before invoking jumpshot. In order to set the CLASSPATH varible, the variables JAVA_HOME and JUMPSHOT_HOME must be determined. The role of configure in the jumpshot directory is to determine these variables, substitute them into the appropriate .in file, create the executable jumpshot or jumpshot12, and place it in the appropriate bin directory. After setting your path to include this directory, you should be able to invoke jumpshot from any directory by typing


    jumpshot  

or
    jumpshot <name of clog file> 



Up: Visualizing Program Behavior Next: Configure Options Previous: Building and Using Jumpshot-3


Configure Options


Up: Jumpshot Next: Installation Instructions Previous: Jumpshot

Jumpshot can be configured in 3 ways:

As part of the { mpich} configure.
The configure in the mpich directory can invoke the configure in the mpe subdirectory which can invoke the configure in the jumpshot subdirectory. This is the default way to configure mpich but can be overridden by configuring mpich with the -nompe option.
As part of the mpe configure.
The configure in the mpe directory can invoke the configure in the jumpshot directory. This is the default if the mpe library was configured with mpich. Otherwise, the configure option --with-jumpshot_home=JUMP_HOME must be given.
By itself.
Jumpshot can be configured by typing configure <configure options> in the jumpshot directory.

By typing


    ./configure --help 

in the top-level jumpshot directory, a list of flags/switches can be viewed.

Mandatory configure flags/switches:

--with-bindir=DIR
Specifies the directory where jumpshot's executable will be located. Without this flag, jumpshot can not be configured. If configuring with MPICH or with just the mpe library. this will be automatically determined by default (but can be overridden).
--with-jumpshot_home=JUMP_HOME
Specifies the path of the top-level directory where jumpshot is installed. Without this directory, jumpshot can not be configured. When configuring with MPICH, this will be automatically determined by default (but can be overriden).

Optional configure flags/switches:
--enable-echo
This switch will turn on strong echoing. The default is no echo.
--with-java=DIR
Specifies the path of JAVA's top-level directory. If omitted, configure will attempt to locate java.
--with-java_version=VERSION
Specifies the version of JAVA. If omitted, configure will attempt to determine your java's version.



Up: Jumpshot Next: Installation Instructions Previous: Jumpshot


Installation Instructions


Up: Jumpshot Next: Internationalization Previous: Configure Options

As noted above, jumpshot can be installed as part of mpich's configure, mpe's configure, or by itself. Below is the instructions and examples for each type of installation.

Configure jumpshot as part of the mpich configure. In this jumpshot installation, no switches and flags are required. The configures in the mpich and mpe directories will locate the necessary information and pass it to the configure in the jumpshot directory. If no options are given to the configure in the mpich directory, jumpshot will be configured with the default values. The user can choose to override this by configuring mpich with the following options:


    -mpe_opts=MPE_OPTS 

    -jumpshot_opts=JUMP_OPTS 

where JUMP_OPTS is one of the choices in Section Configure Options (multiple uses of -jumpshot_opts is not allowed to specify more than one option for jumpshot's configure). See Section Configure Options for MPE_OPTS.

Example 1:
Configure MPICH with the mpe library and jumpshot

In the top-level mpich directory,

    ./configure <mpich configure options> 

    make 

Example 2:
Configure MPICH without the mpe library and with jumpshot
Currently if MPICH is configured without the mpe library, jumpshot does not get configured (since the mpe configure invokes jumpshot's configure). The following are the steps needed to configure MPICH and jumpshot without the mpe library.

In the top-level mpich directory,

    ./configure <mpich configure options> -nompe 

    make 

In the jumpshot subdirectory,


    configure --with-bindir=<directory path of mpich/bin> \ 
      --with-jumpshot_home=<directory path of jumpshot>          

Example 3:
Configure MPICH with the mpe library and with java's directory path given as an option to jumpshot's configure

In the top-level mpich directory,

    ./configure <mpich configure options> \ 
      -jumpshot_opts=--with-jumpshot_opts=--with-java=<directory path of java> 

    make 

It is necessary to include --with-jumpshot_opts since mpich's configure will strip off -jumpshot_opts and mpe's configure will strip off --with-jumpshot_opts and pass the option to jumpshot's configure.
Example 4:
Configure MPICH with the mpe library and override the option jumpshot_home in jumpshot's configure

In the top-level mpich directory,

    ./configure <mpich configure options> \ 
       -jumpshot_opts=--with-jumpshot_opts=--with-jumpshot_home=DIR 

    make 


Configure jumpshot as part of the mpe configure

Example 1:
Configure the mpe library with jumpshot and MPICH (already configured and installed)

In the top-level mpe directory,

    ./configure --with-mpich=<top-level directory of MPICH> \ 
                --with-mpichdev=<library subdirectory of MPICH> 

    make 

Example 2:
Configure the mpe library with jumpshot and SGI's MPI

In the top-level mpe directory,

    ./configure --with-sgi -libdir=<directory path of libdir> \ 
                --with-jumpshot_home=<directory path of jumpshot> 

    make 

Example 3:
Configure the mpe library without jumpshot and IBM's MPI

In the top-level mpe directory,

     ./configure --with-sp -libdir=<directory path of libdir> \ 
                 --enable-jumpshot=no 

     make 

Example 4:
Configure the mpe library with java given as an option to jumpshot's configure

In the top-level mpe directory,

    ./configure <MPI implementation switch> \  

           --with-jumpshot_opts=--with-java=<directory path of java>  

    make 


Configure jumpshot by itself

Example 1:
Configure jumpshot

In the top-level jumpshot directory,

     ./configure -bindir=<directory path of bindir> \ 
                     --with-jumpshot_home=<directory path of jumpshot> 

Example 2:
Configure jumpshot with strong echoing

In the top-level jumpshot directory,

     ./configure -bindir=<directory path of bindir> \ 
                 --with-jumpshot_home=<directory path of jumpshot> \ 
                 --enable-echo=yes 


The log file produced by cpilog is not very interesting, since cpi is such a simple program. Many interesting logfiles can be found in the profiling/upshot/logfiles subdirectory, or jumpshot/lib/logfiles subdirectory. The file cpilog.c demonstrates how to instrument your own code for producing such logs. The User's Guide [9] describes how to link with a version of mpich that produces them automatically. For a short description of the programs in the examples/basic directory, see the README file there.



Up: Jumpshot Next: Internationalization Previous: Configure Options