Category +: Kern-Common

diff -r 43e37759235e -r 51a74ef9ed63 Symbian3/SDK/Source/GUID-9C46DE8B-222D-5E24-AB0D-37BDC8BC0AFB.dita --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Symbian3/SDK/Source/GUID-9C46DE8B-222D-5E24-AB0D-37BDC8BC0AFB.dita Wed Mar 31 11:11:55 2010 +0100 @@ -0,0 +1,139 @@ + + + + + +Category +: Kern-Common +

KERN-COMMON panics are raised by the kernel when various kernel-side utility +functions are called with bad arguments.

+ + + + +

This panic is raised if an invalid descriptor type is given to Kern::KUDesGet() or Kern::KUDesPut().

+ + +

This panic is raised when a length value passed to an 8-bit variant +descriptor member function is invalid. It may be raised by some descriptor +constructors and, specifically, by the Replace() and Set() descriptor +member functions.

+ + +

This panic is raised when the index value passed to the 8-bit variant +descriptor Operator() is out of bounds.

+ + +

This panic is raised when the position value passed to an 8-bit +variant descriptor member function is out of bounds. It may be raised by the Left(), Right(), Mid(), Insert(), Delete() and Replace() descriptor +member functions.

+ + +

This panic is raised if the source passed to Kern::KUDesGet() is +longer than the maximum length of the destination.

+ + +

This panic is raised when expanding or contracting an HBufC8 buffer +using the ReAlloc() or ReAllocL() descriptor +member functions. Specifically, the panic occurs if the new length being specified +is too small to contain the data.

+ + +

This panic is raised by the Replace() member function +of the 8-bit variant descriptor TDes8, when the length +of the source descriptor is negative or exceeds the maximum length of the +target descriptor.

+ + +

This panic is raised when 8-bit variant descriptors are constructed +with negative length values. It may also be raised if the Set(), Repeat() and +the Find() member functions are passed negative length values.

+ + +

This panic is raised when 8-bit variant descriptors are constructed +with negative maximum length values.

+ + +

This panic is raised by Mem::Compare(), Mem::CompareC() and Mem::CompareF() when +the length of the area of memory designated as the left hand area, is negative. +This panic is raised in debug builds only. On the user side this is associated +with the USER category; on the kernel side this is associated with the KERN-COMMON +category.

+ + +

This panic is raised by Mem::Compare(), Mem::CompareC() and Mem::CompareF() when +the length of the area of memory designated as the right hand area, is negative. +This panic is raised in debug builds only. On the user side this is associated +with the USER category; on the kernel side this is associated with the KERN-COMMON +category.

+ + +

This panic is raised by Mem::Copy() when the +length of the area of memory to be copied is negative. This panic is raised +in debug builds only. On the user side this is associated with the USER category; +on the kernel side this is associated with the KERN-COMMON category.

+ + +

This panic is raised by Mem::Move() when the +length of the area of memory to be moved is not a multiple of 4. This panic +is raised in debug builds only. On the user side this is associated with the +USER category; on the kernel side this is associated with the KERN-COMMON +category.

+ + +

This panic is raised by Mem::Move() when the address +of the source for the move operation is not aligned on a 4 byte boundary. +This panic is raised in debug builds only. On the user side this is associated +with the USER category; on the kernel side this is associated with the KERN-COMMON +category.

+ + +

This panic is raised by Mem::Move() when the address +of the target for the move operation is not aligned on a 4 byte boundary. +This panic is raised in debug builds only. On the user side this is associated +with the USER category; on the kernel side this is associated with the KERN-COMMON +category.

+ + +

This panic is raised by Mem::Swap() when the +length of the area of memory to be swapped is negative. This panic is raised +in debug builds only. On the user side this is associated with the USER category; +on the kernel side this is associated with the KERN-COMMON category.

+ + +

This panic is raised by Mem::Fill() and Mem::FillZ() when +the length of the area of memory to be filled is negative. This panic is raised +in debug builds only. On the user side this is associated with the USER category; +on the kernel side this is associated with the KERN-COMMON category.

+ + +

190

This panic is raised when the security policy is found to be corrupt +while performing a security policy check.

+ + + +

\ No newline at end of file