Debugging Dynamic Memory Usage Errors Using NonStop Native Inspect White Paper

8. Does the debugger find leaks in the executable from the startup of the application when
debugging the application in attach mode?
Yes, the debugger finds leaks in the executable from the startup of the executable by default,
when debugging in attach mode.
9. When attempting to view the leak report, the following error occurs:
(eInspect 0,105): info leaks
Scanning for memory leaks...
Error downloading data !
(eInspect 0,105):
What is the cause for this error and what is the work-around?
This error message is displayed when you attempt to view the heap profile or the leak profile
of a debugged process, which is exiting or has exited program execution. As a work-around,
you can place a breakpoint before the program exits and then enter the info leaks
command or the info heap command.
10. What is the work-around if the following error message is displayed while debugging memory?
(eInspect 0,105): info corruption
Current thread is inside the allocator. Try again later.
This error message signifies that the program execution is in a frame that belongs to a Native
Inspect internal leak detection library. When this error is encountered, it is not safe to enter
commands that involve calls to the leak detection library procedures. The user must set the
frame to the last leak detection library frame and enter the finish command before resuming
to debug memory.
24