Open System Services Porting Guide (G06.24+, H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction to Porting
- 2 The Development Environment
- 3 Useful Porting Tools
- 4 Interoperating Between User Environments
- Purpose of Interoperability
- The OSS User Environment
- OSS Commands for the Guardian User
- Guardian Commands for the UNIX User
- OSS Pathname and Guardian Filename Conversions
- Running the OSS Shell and Commands From TACL
- Running Guardian Commands From the OSS Shell
- Running OSS Processes With Guardian Attributes
- Using OSS Commands to Manage Guardian Objects
- 5 Interoperating Between Programming Environments
- 6 OSS Porting Considerations
- 7 Porting UNIX Applications to the OSS Environment
- 8 Migrating Guardian Applications to the OSS Environment
- General Migration Guidelines
- C Compiler Issues for Guardian Programs
- Using New and Extended Guardian Procedures
- Using OSS Functions in a Guardian Program
- Interoperating With OSS Programs
- Starting an OSS Program From the Guardian Environment
- C Compiler Considerations for OSS Programs
- Porting a Guardian Program to the OSS Environment
- How Arguments Are Passed to the C or C++ Program
- Differences in the Two Run-Time Environments
- Which Run-Time Routines Are Available
- Use of Common Run-Time Environment (CRE) Functions
- Replacing Guardian Procedure Calls With Equivalent OSS Functions
- Which IPC Mechanisms Can Be Used
- Interactions Between Guardian and OSS Functions
- 9 Porting From Specific UNIX Systems
- 10 Native Migration Overview
- 11 Porting or Migrating Sockets Applications
- 12 Porting Threaded Applications
- A Equivalent OSS and UNIX Commands for Guardian Users
- B Equivalent Guardian Commands for OSS and UNIX Users
- C Equivalent Inspect Debugging Commands for dbx Commands
- D Equivalent Native Inspect Debugging Commands for dbx Commands
- E Standard POSIX Threads Functions: Differences Between the Previous and Current Standards
- Glossary
- Index
The Development Environment
Open System Services Porting Guide—520573-006
2-20
Using the Debuggers With OSS Files
Running the Debuggers
You can start each debugger by itself and then run programs within it, or you can start
both a debugger and your program at the same time. The following commands both
start the debugger from a TACL prompt, but the second command starts both the
debugger and your program at the same time:
>INSPECT
>RUN INSPECT GPROG
The debugger that is started depends on the program type, as shown in the following
table:
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.
If you are familiar with the dbx debugger on workstations and not familiar with the
Inspect or Native Inspect debugger, see Appendix C, Equivalent Inspect Debugging
Commands for dbx Commands or Appendix D, Equivalent Native Inspect Debugging
Commands for dbx Commands.
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.
Program Type Debugger Started
TNS/R native non-PIC Visual Inspect if a matching client connection has been
established, Inspect otherwise
TNS/R native PIC Visual Inspect if a matching client connection has been
established, Debug otherwise
TNS/E native Visual Inspect if a matching client connection has been
established, Native Inspect otherwise