Native Inspect Manual (H06.03+)

Introducing Native Inspect
Native Inspect Manual—528122-003
1-20
Addressing Symbols for DLLs Loaded at Another
Address
Addressing Symbols for DLLs Loaded at Another Address
If a user loads a symbol file for a DLL before a program call to dlopen() to load the
DLL, Native Inspect uses the preferred address of the DLL as the basis for symbol
address calculations. Then, when the DLL is loaded, Native Inspect again attempts to
load the symbols using the actual load address for the DLL.
Setting Breakpoints
Native Inspect does not support the ability to set breakpoints on DLL functions before
the DLL is loaded.
Handling Events
When Native Inspect receives an event, it informs you what event has occurred and
then updates the debugging context (that is, information specific to the current process,
such as breakpoints, loaded DLLs, and the current register values).
The type of events that have the most impact on debugging with Native Inspect are
debugging events, which typically suspend a program under debugger control. For
example, a breakpoint is a debugger-induced debugging event.
Specific responses to significant events are listed in Table 1-2.
Assessing Your Location After an Event
If you are uncertain about your current program location after an event occurs, you can
list the current frame by using the frame command, select-frame command:
(eInspect 6,679): frame
#0 test_complexTypes() () at \SYS03.$D007.SYMBAT1.SCXXTST:424
424 printf( "%s test_complexTypes\n", getStepPrefix( 1 ) );