noft Manual (G06.26+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction
- 2 noft Utility
- 3 noft Options
- Break Key
- ! (Exclamation Point)
- CD
- COMMENT
- DUMPADDRESS or DA
- DUMPOFFSET or DO
- DUMPPROC or DP
- DYNSTR2
- ENV
- EXIT or E
- FC
- FILE or F
- HELP or ?
- HISTORY or H
- LAYOUT
- LIBLIST
- LISTATTRIBUTE or LA
- LISTCOMPILERS or LC
- LISTOPTIMIZE or LO
- LISTPROC or LP
- LISTSOURCE or LS
- LISTSRLEXPORTS or LLE
- LISTSRLFIXUPS or LLF
- LISTSRLINFO or LLI
- LISTUNREFERENCED or LUR
- LISTUNRESOLVED or LU
- LOG
- OBEY
- OUT
- QUIT or Q
- RESET
- SET
- SHOW
- SYSTEM or VOLUME
- XREFPROC or XP
- 4 noft Diagnostic Messages
- 5 ar Utility
- 6 ar Diagnostic Messages
- A Sample nld and noft Session
- B Converting From Binder to noft
- C Native Object File Structure
- Glossary
- Index

noft Utility
noft Manual—528273-001
2-7
Debugging With noft
Debugging With noft
The dumping options (listed in Table 2-2 on page 2-4) can be useful when debugging
optimized native object code, especially when you must debug code at the RISC
instruction-level.
Note. You must use Visual Inspect, rather than Inspect, to debug PIC executable files.
Example 2-3. C Program
long compute(long a[]);
int main (void)
{
long z[10];
long x;
x=compute(z);
return 0;
}
long compute(long a[])
{
long b;
int c,i;
b=0;
for (i=0; i<20; i++)
b += a[i];
return b;
}