C/C++ Programmer's Guide (G06.27+, H06.08+, J06.03+)

Recovery
In the TNS environment, the program might have written data in the upper 32K words of the
user data segment or in the extended segment. The upper 32K words of the user data area are
reserved for CRE and run-time library data. In a small-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 a symbolic debugger to help
isolate the problem or consult your system administrator.
If this error occurs in the native environment, use a symbolic debugger 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
Released space address is 0
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
Released space not allocated
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
Heap corrupted ( 32-bit_octal_address )
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 a symbolic debugger to help isolate the problem or consult your system administrator.
If this error occurs in the native environment, check the program’s logic. Use a symbolic debugger
to help isolate the problem or consult your system administrator.
36
Invalid operation for heap
Heap-Management Messages 371