enoft Manual

eNOFT Manual—527507-005

B-1

Differences Between eNOFT and

NOFT

Architecture

NOFT supports TNS/R object files which include ELF and COFF object file structures.

eNOFT supports TNS/E architecture, which is exclusively ELF.

All TNS/E object files are big endian files with DWARF2 debugging symbol tables.

Code on the TNS/E platform is always little endian.

When accessing a code area of the object file (for example, .text), eNOFT displays in

16-byte "bundles" whereas NOFT displays in units of 4-byte "words". However eNOFT

will display virtual addresses in the same format as NOFT: 32-bit hexadecimal values.

Debugging

NOFT uses the Third Eye symbol table where some of its tables are used for linking;

eNOFT uses the DWARF2 symbol table which does not contain such information used

by the object file linker "eld" or runtime loader "rld" . One consequence of this

difference is in the behavior of eNOFT on stripped files. Commands that require the use

of the debugging information are not supported on stripped files. Because the meaning

of stripping is different between TNS/R and TNS/E architectures, eNOFT does not

support the same commands that NOFT supports. See SET and RESET Commands on

page B-1 and subsequent tables for details.

Displays

NOFT typically displays listings in a center-justified format. eNOFT displays are typically

left-aligned with the object file offset value for the specified target section in the

heading.

Summary of eNOFT Commands

The following tables list eNOFT commands and their NOFT equivalents.

Table B-1. SET and RESET Commands

NOFT eNOFT Alias Options

RESET <set-cmd>

SET <set-cmd> OFF RESET - [* | set-cmd]

SET CASE SET CASE SC {OFF | ON}