TNS/E Native Application Conversion Guide

Introduction to Native Mode
TNS/E Native Application Conversion Guide—529659-003
1-11
Visual Inspect
For code compiled at optimization level 0 (no optimization) or optimization level 1
(intermediate optimization), you can perform the same operations for native processes
(using Visual Inspect) as for TNS process (using Inspect), including:
•
Step through code
•
Set breakpoints
•
Display source
•
Display variables
In addition, H-series Visual Inspect provides these machine-level capabilities:
•
Set instruction breakpoints
•
Display instruction code
•
Display and modify data using a numeric (nonsymbolic) address
•
Modify, format, and monitor registers
•
Display and format data buffers as SPI or EMS buffers
Differences in the TNS and native process architectures result in differences in
registers and address ranges. Unlike TNS interpreted and accelerated code, TNS
architecture-specific constructs, such as TNS environment registers, do not exist in
native mode code.
At optimization level 2 (full optimization), machine-level debugging might be necessary
because of the effects of optimization. For example, variables might remain in registers
and never be written to memory. For more details on compiler optimization, see
Determining Optimization Levels on page 2-5.
The Inspect and Visual Inspect symbolic debuggers differ in these respects:
•
User interface
The Inspect debugger uses a line-oriented command interpreter, while the Visual
Inspect debugger uses a GUI environment consisting of menus and icons that you
can select and click to perform tasks.
•
Features and functions
Visual Inspect supports many but not all Inspect capabilities. Many commands
have become part of the GUI (for example, the ENV command).
For details on Visual Inspect capabilities, see the Visual Inspect online help.