* ORNL PVM * * ORNL PVM * * ORNL PVM * * ORNL PVM * * ORNL PVM * * ORNL PVM * -------------------------------------------------------------------------- | Instructions for PVM(e) debugging: | To be used AFTER first running the interactive example as is (without debugging). -------------------------------------------------------------------------- 0) Edit the file manager.f so that the pvmfspawn command takes on the PVMDEBUG argument (i.e. replace PVMDEFAULT by PVMDEBUG). Without this change, the spawned tasks will not be debuggable. 1) Make sure you are in the ORNL PVM environment, type: prompt> startpvm (If pvm is your default environment, set in your .cshrc file, and you haven't switched to pvme, then you can skip the startpvm step. See ../README.FIRST for more information.) In your copy of the sample directory, type: prompt> make -f make.pvm The makefile will direct the compilation and linking of the programs. The executables are created in the current directory in this example, but this can be changed to the default executable directory, $HOME/pvm3/bin/RS6K, by editing the EXEDIR entry in the makefile. It's highly recommended that you *first* run through the example "as is", and then experiment with modifications after you've confirmed that the basic example works for you. 2) Generate a hostfile for the interactive pool. This can be easily done by running the command: prompt> set_pvm_pool In an interactive setting, this command will generate a hostfile (named "hostfile") which contains the 4 available interactive nodes, and uses the current working directory as the PVM working directory and executable path. (The hostfile can later by modified to suit your needs.) 3) In the sample directory, start the PVM daemon on the nodes of the interactive pool by typing: prompt> pvmd3 hostfile & <-- NOTE: the ampersand is important! If omitted, you must push the job to the background to continue. 4) Check the configuration through the pvm console: prompt> pvm [RETURN] pvmd already running. pvm> conf [RETURN] 4 hosts, 1 data format HOST DTID ARCH SPEED grand17.nist.gov 40000 RS6K 1000 grand18.nist.gov 80000 RS6K 1000 grand19.nist.gov c0000 RS6K 1000 grand20.nist.gov 100000 RS6K 1000 pvm> quit [RETURN] prompt> (Other responses, such as only one host being listed, are a sign that something has not gone right. Please contact karin@cam.nist.gov.) 5) Run the program under the debugger by typing: prompt> debug manager You will be prompted to enter information about the location of your source files, and any global breakpoints you may want to set. For the provided example, enter a single period (meaning current directory) for the location of source files, and a null line for global breakpoints. Use the standard dbx commands (run, cont, list, stop at , etc.) to examine the manager program. When the pvmfspawn call is reached, for each spawned process, an X-window dbx session will be generated. Standard dbx commands may also be entered in these spawned dbx sessions. 6) To quit, enter quit in each spawned debug window, and quit in the manager debug window. Do NOT forget to HALT the pvm daemon (especially with PVMe sessions!) prompt> pvm [RETURN] pvm> halt [RETURN] prompt> 8) Clean up... type: prompt> make -f make.pvm new This will remove the executable, object, output and error files, to restore the directory to its original state. -------------------------------------------------------------------- | Again, | please direct any questions, comments or suggestions | to karin@cam.nist.gov. --------------------------------------------------------------------