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
Open System Services Porting Guide—520573-006
C-1
C
Equivalent Inspect Debugging
Commands for dbx Commands
The Inspect debugger displays source from OSS files. Because line numbers
automatically increment for OSS files but not for Guardian files, line numbers for
corresponding converted source files might differ. If your file was originally compiled in
an OSS environment, the line numbers do correspond.
Table C-1 presents a mapping of dbx commands to Inspect commands to help OSS
programmers who are more familiar with dbx than with the Inspect debugger. For more
information about using the Inspect debugger, refer to the Inspect Manual.
Table C-1. Equivalent Inspect Commands for dbx Commands (page 1 of 2)
dbx Inspect dbx Inspect
/ Source Search quit Stop/Exit
? Source Search record
input
Log Input
address Display, Icode record
output
Log Output
alias ADD ALIAS and
LIST ALIAS
rerun N.A.
assign Modify return Step Out
catch N.A. run Resume
cont Resume set N.A.
conti N.A. sh N.A.
delete Delete..., Clear source Obey
down Scope status List Break
dump Info Scope, Trace
Arguments
step Step In
edit N.A. stepi Step Icode
file N.A. stop Break
func Scope stopi Break
goto Resume At trace Break ... THEN ...
help Help tracei N.A.
history History unalias Delete Alias
ignore Modify Signal unset N.A.
list Source up Scope
next Step use Source Assign