12 <panic_description><p>This panic is raised in a call to the RHeap member functions, AllocLen(), Free(), FreeZ(), ReAlloc(), ReAllocL(), Adjust() and AdjustL(), when a pointer passed to these functions does not point to a valid cell. On the user side this is associated with the USER category; on the kernel side this is associated with the KERN-HEAP category. </p></panic_description> |
12 <panic_description><p>This panic is raised in a call to the RHeap member functions, AllocLen(), Free(), FreeZ(), ReAlloc(), ReAllocL(), Adjust() and AdjustL(), when a pointer passed to these functions does not point to a valid cell. On the user side this is associated with the USER category; on the kernel side this is associated with the KERN-HEAP category. </p></panic_description> |
16 <panic_description><p>This panic is raised when attempting to set a new debug failure mode on a heap with an invalid argument. For example, if aBurst > KMaxTUint6 when invoking __UHEAP_BURSTFAILNEXT when a RHeap object is used for the user heap. On the user side this is associated with the USER category; on the kernel side this is associated with the KERN-HEAP category. </p></panic_description> |
16 <panic_description><p>This panic is raised when attempting to set a new debug failure mode on a heap with an invalid argument. For example, if aBurst &gt; KMaxTUint6 when invoking __UHEAP_BURSTFAILNEXT when a RHeap object is used for the user heap. On the user side this is associated with the USER category; on the kernel side this is associated with the KERN-HEAP category. </p></panic_description> |