Tns/E Native Object Files; The Object File Format; Basic Properties Of Object Files - HP eld Manual

A

TNS/E Native Object Files

This appendix contains the following information:

The Object File Format

Code and Data Sections
application source code, possibly with additions by the compiler or linker.
Relocation Tables
relocation tables?
Finding Information About Procedures and Subprocedures in Linkfiles
to the .procinfo and .procnames sections of linkfiles.
The DWARF Symbol Table
Cobol compiler.
Archives - contains an extension of material covered in a previous section of this
manual.
Tools That Work With Object Files
system tools use object files.
The Object File Format
Some of this general information may also be found in Sections One and Two of this
manual, but this appendix provides much more detail.

Basic Properties of Object Files

User versions of TNS/E tools may run in the following places:
•
All TNS/E versions of the HP NonStop operating system, including both the
Guardian and OSS environments.
•
Some TNS/R versions of the HP NonStop operating system, at least in the
Guardian environment.
•
Appropriate versions of the Windows operating system on PC's.
TNS/E object files only run on TNS/E.
On Guardian and OSS, object files are unstructured files that are "odd unstructured",
the same as in TNS/R.
On Guardian and OSS, TNS/E object files have the file code 800.
TNS/E object files use the 64-bit version of the ELF file format.
TNS/E object files are big endian. This means that all their data is big endian.
- the types of object files and their content.
- the "ordinary" code and data sections that come from
- when code is relocated, who resolves the address and prepares
- this table contains information used by debuggers and the
- a quick look at which HP NonStop operating
eld Manual—527255-009
A-1
- an introduction