1 <?xml version='1.0' encoding='UTF-8'?>

     2 <panic_category>

     3   <category_name>Kern-Heap</category_name>

     4   <category_description> &lt;p&gt;KERN-HEAP panics are raised by the kernel when bad parameters are passed to kernel-side heap functions. &lt;/p&gt;</category_description>

     5   <panics>

     6     <panic>

     7       <panic_id>39</panic_id>

     8       <panic_description>&lt;p&gt;This panic is raised when the size specified for the new heap is smaller than the permitted minimum; it must be at least the size of a RHeap object. On the user side this is associated with the USER category; on the kernel side this is associated with the KERN-HEAP category. &lt;/p&gt;</panic_description>

     9     </panic>

    10     <panic>

    11       <panic_id>42</panic_id>

    12       <panic_description>&lt;p&gt;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. &lt;/p&gt;</panic_description>

    13     </panic>

    14     <panic>

    15       <panic_id>213</panic_id>

    16       <panic_description>&lt;p&gt;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. &lt;/p&gt;</panic_description>

    17     </panic>

    18   </panics>

    19 </panic_category>