Debugging Dynamic Memory Usage Errors Using HP WDB v6.3 (5900-2181, August 2012)

(gdb) 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 GDB
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.
Example 25 (page 82) illustrates the use of the finish to resume memory debugging when
the program execution is in a frame that belongs to the GDB internal leak detection library.
14 Does memory heap or leak detection work if libmallocng is used for heap allocation
management instead of libc?
Yes. On Itanium systems, the heap or leak detection works if libmallocng is used for heap
management. The arena information cannot be obtained when the application uses
libmallocng.
15 The batch mode RTC sometimes crashes when the application has atfork handlers.
The batch mode RTC might have problems if the application has atfork handler. This issue
has been resolved from version 6.1 of librtc on Itanium systems.
Index
A
Access Errors, 8
Attach Mode, 58
B
Batch Mode , 49
Batch Mode Configuration File, 52
BATCH_RTC, 49
C
catch nomem , 23
D
Dangling pointerinfo dangling, 43
Debugging Memory Using WDB GUI, 61
E
Environment Variables for Batch Mode , 49
Error Injection, 23
Event Monitoring, 29
H
Heap Corruption, 7
Heap Profiling, 11
I
Incremental Heap Profiling, 13
info corruption, 36, 41
info heap <filename>, 11
info heap arenas, 16
info heap high-mem , 33
info heap process, 16
info heap-interval <filename>, 13
info leaks, 21
Intended Audience, 5
84 Index