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
D-1
D
Equivalent Native Inspect
Debugging Commands for dbx
Commands
Native Inspect is the H-series command line symbolic debugging tool. The Native
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 D-1 presents a mapping of dbx commands to Native Inspect commands to help
OSS programmers who are more familiar with dbx than with the Native Inspect
debugger. For more information about using the Native Inspect debugger, refer to the
Native Inspect Manual.
Table D-1. Equivalent Native Inspect Commands for dbx
Commands (page 1 of 2)
dbx Native Inspect dbx Native Inspect
/ quit exit
? record
input
log
address print, output record
output
alias use TCL script rerun
assign set, modify return
catch run continue
cont continue, resume set set
conti sh
delete delete source use TCL script
down down status info breakpoints
dump bt ? step step
edit stepi stepi
file stop break
func frame stopi break
goto jump trace info stack, bt
help help tracei
history history unalias delete alias