Open System Services Porting Guide (G06.29+, H06.06+, J06.03+)

The debugger that is started depends on the program type, as shown in the following table:
Starts This DebuggerProgram Type
Visual Inspect if a matching client connection has been established, Inspect
otherwise
TNS/R native non-PIC
Visual Inspect if a matching client connection has been established, Debug
otherwise
TNS/R native PIC
Visual Inspect if a matching client connection has been established, Native Inspect
otherwise
TNS/E native
The following commands are entered from the OSS shell. The first command starts the debugger.
The second command starts both the debugger and your program at the same time. The debugger
started depends on the program type, as shown in the preceding table.
$ gtacl -p inspect
$ run -debug -inspect=on ossprog
Additionally, you can start Visual Inspect with one of the following commands:
>RUNV WSADDR=MYPC GPROG (Guardian)
$ runv -wsaddr=mypc ossprog (OSS)
These commands start the Visual Inspect debug session on the workstation MYPC.
NOTE: Beginning with the H06.24 and J06.13 RVUs, 64-bit OSS programs are supported. The
Native Inspect debugger starts when specifying a 64-bit OSS program as the ossprog parameter
for either the run -debug or runv command, because Visual Inspect does not currently support
64-bit programs.
OSS Environment Considerations
The following usage considerations provide information specific to debugging in the OSS
environment:
• Line numbers might be different when using source assigns between Guardian EDIT files and
OSS files.
• A single Inspect or Native Inspect command cannot accept both Guardian and OSS filenames,
with the exception of the Inspect SOURCE ASSIGN.
• Core files, known as save or saveabend files in Inspect and as snapshot files in Native Inspect,
are named ZZSAnnnn.
• You cannot use a Guardian filename while the Inspect systype is OSS.
Using the noft and enoft Utilities on Native Program Files
Three additional development utilities, the native linkers (ld, eld, and nld) and the native object
file tools (noft and enoft), are used with native object files. The Binder program is used on TNS
object files. For working with native object files, these tools do not offer identical features, but they
offer similar features.
The nld utility links non-position-independent code (non-PIC) TNS/R native object files with libraries
specified on the c89 command line to create an executable program. The ld utility links TNS/R
PIC object files with dynamic-link libraries (DLLs) to create a PIC loadfile. The eld utility links TNS/E
PIC object files with DLLs to create a PIC loadfile. The PIC loadfile can be executed after being
loaded into memory by the rld utility.
The noft utility reads and displays information from TNS/R native object files, providing some
debugging options not available with the Inspect debugger. The enoft utility reads and displays
information from TNS/E native object files, providing some debugging options not available with
the Native Inspect debugger.
46 The Development Environment