Cross-Debugging

Using the SAS/C Debugger in a Cross-Development Environment

To debug a program in the cross-development environment, you should perform the following steps:

Compile the program on the host workstation, using the -g option to specify generation of a debugger file.
Create a load module for your program that resides on the target mainframe.
Use the NFSLOGIN command to access the NFS server network from the mainframe. See Logging on to the NFS Network for more information.
Mount the workstation's file system from your mainframe client using one of the methods described in Accessing Remote File Systems.
Invoke the debugger, using set search commands in the debugger PROFILE to specify search lists for the source, include, and debugger files.
Note: The debugger uses standard fopen calls to access these files. If you encounter difficulty accessing files, the problem may be caused by your remote file mount, and the failure to properly match the mount point and the templates in the debugger's search lists.

If you do not use the set search command to specify search lists, the debugger resorts to its default search mechanism, using the filenames contained in the object and debugger files to locate files. By default, the debugger uses the path : filename style prefix with workstation filenames. The path : prefix is described in Appendix 1.

The next section explains how to use the debugger's set command to specify search lists and a cache location for the debugger file. You should refer to the SAS/C Debugger User's Guide and Reference for additional information about the SAS/C Debugger.

Chapter Contents
Previous
Next
Top of Page