CRE Programmer's Guide

Run-Time Diagnostic Messages
Common Run-Time Environment (CRE) Programmer’s Guide—528146-004
10-13
Heap-Management Messages
memory model, the heap is allocated in the lower 32K words of the user data segment.
In a large memory model, the heap is allocated in an extended memory segment.
Check the program’s logic. Use Inspect or Visual Inspect to help isolate the problem or
consult your system administrator.
If this error occurs in the native environment, use Native Inspect or Visual Inspect to
help isolate the problem. In the case of “Process heap size is 0,” specify the existence
of a user heap when building your program.
33
Cause. The address of a block of memory to return to the heap was zero.
Effect. Program behavior is language and application dependent.
Recovery. Correct the program to pass the correct address.
34
Cause. The address of a block of memory to return to the heap did not point to a block
allocated from the heap.
Effect. Program behavior is language and application dependent.
Recovery. Correct the program to return the correct pointer value.
35
Cause. The CRE or a run-time library found invalid information at location
32-bit_octal_address of the heap.
Effect. Program behavior is language and application dependent.
Recovery. The program might have written data over the heap. In a small-memory
model, the heap is allocated in the lower 32K words of the user data segment, just
below the run-time stack. In a large memory model, the heap is allocated in an
extended memory segment. Check the program’s logic. Use Inspect or Visual Inspect
to help isolate the problem or consult your system administrator.
If this error occurs in the native environment, check the program’s logic. Use Native
Inspect or Visual Inspect to help isolate the problem or consult your system
administrator.
Released space address is 0
Released space not allocated
Heap corrupted ( 32-bit_octal_address )