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
Equivalent Inspect Debugging Commands for dbx
Commands
Open System Services Porting Guide—520573-006
C-2
Table C-2 lists Inspect commands that do not have a dbx command equivalent.
nexti Step Icode whatis Info Identifier
playback
input
Obey when Break ... IF ... THEN ...
playback
output
N.A. where Trace
print Display whereis Match Identifier, Match
Scope
printf N.A. which N.A.
printregs Display Register
Table C-2. Inspect Commands Without a dbx Counterpart
Command Description
ADD PROGRAM Add a program to the current Inspect session
DISPLAY Inspect’s DISPLAY command has a richer set of options and
arguments than dbx’s print command
INFO OBJECT Displays information about the current process’s object files
INFO OPENS List files opened by current process
INFO SEGMENT List currently allocated extended segments
LIST PROGRAM Inspect is able to debug multiple programs
SELECT PROGRAM Select the current program. This can also be used to load new
symbol files for the specified program
Table C-1. Equivalent Inspect Commands for dbx Commands (page 2 of 2)
dbx Inspect dbx Inspect