Enum TCdtPanic

A thread has called User::Invariant().

Typically, User::Invariant() is called when a test for a class invariant fails, i.e. when a test which checks that the internal data of an object is self-consistent, fails.

Check the design and implementation of your class.

Not used.

Not used.

ATDateTime object has been constructed with an invalid date or time field.

Not used.

Not used.

Not used.

A panic raised by the Ptr() member function of a 16-bit descriptor if the descriptor is invalid.

The length value passed to a 16-bit variant descriptor member function is invalid.

This panic may be raised by some descriptor constructors and, specifically, by the Replace() and Set() descriptor member functions.

The index value passed to the 16-bit variant descriptor Operator[] is out of bounds.

The position value passed to a 16-bit variant descriptor member function is out of bounds.

The panic can be raised by the Left(), Right(), Mid(), Insert(), Delete() and Replace() member functions of TDes16.

An operation to move or copy data to a 16-bit variant descriptor, will cause the length of that descriptor to exceed its maximum length.

This may be caused by any of the copying, appending or formatting member functions but, specifically, by the Insert(), Replace(), Fill(), Fillz(), and ZeroTerminate() descriptor member functions. It can also be caused by the SetLength() function.

The format string passed to the 16-bit variant descriptor member functions Format() and AppendFormat() has incorrect syntax.

An invalid variable list has been passed to the AppendFormatList() member function of the 16-bit variant descriptor TDes16, when the format is S or s.

This panic is raised in debug builds only.

This panic is raised when expanding or contracting an HBufC16 buffer using the ReAlloc() or ReAllocL() descriptor member functions and the new specified length is too small to contain the data.

Not used.

In a call to the Replace() member function of the 16-bit variant descriptor TDes16,the length of the source descriptor is negative or exceeds the maximum length of the target descriptor.

A 16-bit variant descriptor is being constructed with a negative length value.

This panic may also be raised if the Set(), Repeat() and the Find() member functions are passed negative length values.

A 16-bit variant descriptor is being constructed with a negative maximum length value.

A panic raised by the Ptr() member function of an 8-bit descriptor if the descriptor is invalid.

The length value passed to an 8-bit variant descriptor member function is invalid.

This panic may be raised by some descriptor constructors and, specifically, by the Replace() and Set() descriptor member functions.

The index value passed to the 8-bit variant descriptor Operator[] is out of bounds.

The position value passed to an 8-bit variant descriptor member function is out of bounds.

The panic can be raised by the Left(), Right(), Mid(), Insert(), Delete() and Replace() member functions of TDes8

An operation to move or copy data to an 8-bit variant descriptor, will cause the length of that descriptor to exceed its maximum length.

This may be caused by any of the copying, appending or formatting member functions but, specifically, by the Insert(), Replace(), Fill(), Fillz(), and ZeroTerminate() descriptor member functions. It can also be caused by the SetLength() function.

The format string passed to the 8-bit variant descriptor member functions Format() and AppendFormat() has incorrect syntax.

An invalid variable list has been passed to the AppendFormatList() member function of the 8-bit variant descriptor TDes8, when the format is S or s.

This panic is raised in debug builds only.

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

Not used.

In a call to the Replace() member function of the 8-bit variant descriptor TDes8,the length of the source descriptor is negative or exceeds the maximum length of the target descriptor.

An 8-bit variant descriptor is being constructed with a negative length value.

This panic may also be raised if the Set(), Repeat() and the Find() member functions are passed negative length values.

An 8-bit variant descriptor is being constructed with a negative maximum length value.

Not used.

It is raised by TRawEvent::Pos() when the event is not a mouse/pen type event.

This panic is raised in debug builds only.

It is raised by TRawEvent::ScanCode() when the event is not a key down or key up event.

This panic is raised in debug builds only.

It is raised by TRawEvent::Modifiers() when the event is not a modifier update event.

This panic is raised in debug builds only.

This panic is raised by the default At() virtual member function of TKey.

The function is intended to be overridden by a derived class.

This panic is raised by the default Swap() virtual member function of TSwap.

The function is intended to be overridden by a derived class.

The index value passed to the operator[] of a TUidType is negative or is greater than or equal to KMaxCheckedUid.

The length of the descriptor passed to the Set(TDesC8&) member function of TCheckedUid is not equal to the size of a TCheckedUid object.

The size specified of a 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 assciated with the USER category; on the kernel side this is associated with the KERN-HEAP category.

Not used.

In a call to UserHeap::ChunkHeap(), the value defining the minimum length of the heap is greater than the value defining the maximum length to which the heap can grow.

In a call to the RHeap member functions, AllocLen(), Free(), FreeZ(), ReAlloc(), ReAllocL(), Adjust() and AdjustL(), a pointer passed to these functions does not point to a valid cell.

On the user side this is assciated with the USER category; on the kernel side this is associated with the KERN-HEAP category.

In a call to the Adjust() and AdjustL() member functions of RHeap, a heap cell is being shrunk and the amount by which the cell is being shrunk is less than the current length of the cell.

In a call to the Free() and FreeZ() member functions of RHeap,the cell being freed overlaps the next cell on the free list (i.e. the first cell on the free list with an address higher than the one being freed).

In a call to the Free() and FreeZ() member functions of RHeap, the cell being freed overlaps the previous cell on the free list (i.e. the last cell on the free list with an address lower than the one being freed).

In a call to the ReAlloc() and ReAllocL() member functions of RHeap, the cell being reallocated overlaps the next cell on the free list (i.e. the first cell on the free list with an address higher than the one being reallocated).

In a call to the Alloc(), AllocL() or AllocLC() member functions of RHeap, an attempt has been made to allocate a cell from a heap, using an unsigned size value which is greater than or equal to the value of KMaxTInt/2.

This panic may also be raised by the heap walker when it finds a bad allocated heap cell size.

This panic is raised by the heap walker when it finds a bad allocated heap cell address.

This panic is raised by the heap walker when it finds a bad free heap cell address.

Not used.

A call has been made to the __DbgMarkEnd() member function of RHeap, when there has been no corresponding call to the __DbgMarkStart() member function.

This panic is also raised when there are more calls to __DbgMarkEnd() than to __DbgMarkStart(). These functions are part of the debug assistance provided by the RHeap class.

This panic is raised in debug builds only.

In a call to the Adjust() and AdjustL() member functions of an RHeap, the offset from the start of the cell being stretched or shrunk is a negative value.

Not used.

In a call to the ReAlloc() and ReAllocL() member functions of an RHeap, the new size for the cell being reallocated is a negative value.

This panic is caused by the UserHeap::ChunkHeap() static function when the value defining the minimum length of the heap is negative.

This panic is caused by the UserHeap::ChunkHeap() static function when the value defining the maximum length to which the heap can grow, is negative.

This panic is raised when closing a shared heap using the Close() member function of RHeap and the access count is zero or negative.

A zero or negative access count suggests that an attempt is being made to close the heap too many times.

This panic is raised when opening a heap for shared access using the Open() member function of RHeap and the heap type is not EChunkNormal.

This panic is raised by the UnGet() member function of the 8-bit variant lexical analyzer, TLex8, if the character position is already at the start of the string.

This panic is raised by the Inc() member function of the 8-bit variant lexical analyzer, TLex8, if the resulting character position lies before the start of the string or after the end of the string.

This panic is raised by the SkipAndMark() member function of the 8-bit variant lexical analyzer, TLex8, if the resulting character position lies before the start of the string, or after the end of the string.

Not used.

This panic is raised by the ValidateMark() member function of the 8-bit variant lexical analyzer, TLex8, if the position of the extraction mark lies before the start of the string or after the end of the string.

This panic is raised by the UnGet() member function of the 16-bit variant lexical analyzer, TLex16, if the character position is already at the start of the string.

This panic is raised by the Inc() member function of the 16-bit variant lexical analyzer, TLex16, if the resulting character position lies before the start of the string or after the end of the string.

This panic is raised by the SkipAndMark() member function of the 16-bit variant lexical analyzer, TLex16, if the resulting character position lies before the start of the string or after the end of the string.

Not used.

This panic is raised by the ValidateMark() member function of the 16-bit variant lexical analyzer, TLex16, if the position of the extraction mark lies before the start of the string or after the end of the string.

This panic is raised by the TDateSuffix constructor or its Set() member function when the suffix index specified is negative or is greater than or equal to the value KMaxSuffixes.

The index is used to access a locale dependent table of suffix characters, which can be appended to the dates of the month (e.g. the characters "st" for 1st, "nd" for 2nd, "st" for 31st).

This panic is raised when attempting to complete a client/server request and the RMessagePtr is null.

Not used.

This panic is raised by the Send() and SendReceive() member functions of RSessionBase, the client interface for communication with a server, when the specified operation code identifying the required service is either negative or a value greater than KMaxTint.

This panic is raised by the Receive() member function of RServer, the handle to the server, when the attempt to receive a message for the server, synchronously, fails.

Not used.

This panic is raised by the constructor of a singly linked list header, a TSglQue or by the SetOffset() member function when the specified offset is not 4 byte aligned, i.e. when it is not divisible by 4.

This panic is raised when attempting to remove an object from a singly linked list, using the Remove() member function of TSglQue, when that object is not in the list.

Not used.

This panic is raised by the constructor of a doubly linked list header, a TDblQue or by the SetOffset() member function, when the specified offset is not 4 byte aligned, i.e. when it is not divisible by 4.

This panic is raised by a call to either the First() or the Last() member functions of a doubly linked list, a TDblQue, which return pointers to the first and last element in the list respectively; the panic occurs when the list is empty.

This panic is raised in debug builds only.

This panic is raised by the post increment operator, operator++, the post decrement operator, operator- and the return current element operator, operator T*, of the doubly linked list iterator, a TDblQueIter; the panic occurs when the element returned by these operators is not in the list.

Typically, this is caused by the removal of the element from the list prior to calling these operators.

This panic is raised in debug builds only.

This panic is raised by the get rectangle operator, operator[], of a clipping region, derived from the abstract base class TRegion.

The panic occurs when the index, which refers to the specific rectangle within the region, is greater than or equal to the number of rectangles contained within the region (as returned by the Count() member function).

The index must be strictly less than the number of contained rectangles.

This panic is raised when sorting the rectangles within a clipping region, derived from the abstract base class TRegion, using the Sort() member function of TRegion.

The panic occurs when the region is invalid.

This panic is raised in debug builds only.

This panic occurs when the Kernel sends a message to the Kernel server and this completes with an error, i.e. an error code which is not KErrNone.

This panic is raised by the Panic() member function of RTest, the test class.

This panic is raised by the CheckConsoleCreated() member functions of RTest and RTestJ, the test classes, when the creation of a console, as derived from a CConsoleBase, fails.

This panic is raised by the static function User::After() when the specified time interval is negative.

This panic is raised when the time interval passed to the After() member function of RTimer is negative.

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 assciated 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 assciated 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 assciated 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 assciated 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 assciated 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 assciated 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 assciated 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 assciated with the USER category; on the kernel side this is associated with the KERN-COMMON category.

The value for the number of records to be sorted passed to User::QuickSort() is negative.

The value for the number of records taking part in the search passed to User::BinarySearch() is negative.

This panic is raised by the constructor of the base key class, TKey.

It occurs when the offset value passed to the constructor is negative. As TKey is an abstract class, i.e. objects of type TKey are not intended to be explicitly constructed, look at the offset value passed to the constructors of derived classes such as TKeyArrayFix, TKeyArrayVar, and TKeyArrayPak for the cause of the panic.

This panic is raised when a local or global chunk is created using the RChunk member functions: CreateLocal(), CreateGlobal(), CreateDoubleEndedLocal() and CreateDoubleEndedGlobal().

It occurs when the value for the maximum size to which this chunk can be adjusted, is negative.

This panic is raised when a local or global chunk is created using the RChunk member functions: CreateLocal() and CreateGlobal().

It occurs when the value for the number of bytes to be committed to this chunk on creation, is negative.

This panic is raised when a local or global chunk is created using the RChunk member functions: CreateLocal() and CreateGlobal().

It occurs when the value for the number of bytes to be committed to this chunk on creation is greater than the value for the maximum size to which this chunk can be adjusted.

This panic is raised when changing the number of bytes committed to a chunk by calling the Adjust() member function of RChunk.

The panic occurs when the value passed to the function is negative.

Not used.

Not used.

This panic is raised when a local or global semaphore is created using the RSemaphore member functions: CreateLocal() and CreateGlobal(), and the value for the initial semaphore count is negative.

This panic is raised when a semaphore is signaled using the Signal(TInt aCount) member function and the count value is negative.

This panic is raised when a critical section is signalled using the Signal() member function and the call to Signal() is not matched by an earlier call to Wait(), which suggests that this is a stray signal.

Not used.

This panic is raised when creating a thread using the Create() member functions of RThread.

The panic occurs when the value of the stack size passed to these functions is negative.

This panic is raised when creating a thread using the Create() member functions of RThread.

The panic is only raised by those variants of Create() that create a new heap for the new thread. The panic occurs if the minimum heap size specified is less than KMinHeapSize.

This panic is raised when creating a thread using the Create() member functions of RThread.

The panic is only raised by those variants of Create() which create a new heap for the new thread. The panic occurs if the minimum heap size specified is greater than the maximum size to which the heap can grow.

This panic is raised by the Alloc() and AllocL() member functions of class RRef when the size value passed is negative.

This panic is raised by:

1. the constructor of a time representation object, a TTime, which takes a text string, when the format of that text string is incorrect or represents an invalid date/time.

2. the Parse() member function of a time representation object, a TTime, if the century offset value is either negative or is greater than or equal to 100.

3. the Time::DaysInMonth() function, if an invalid month value is passed.

This panic is raised by member functions of TBusLocalDrive when no connection has been made to a local drive.

This panic is raised in debug builds only.

This panic is raised when attempting to connect to a local drive using the Connect() member function of TBusLocalDrive, and the specified drive number is out of range, i.e. the drive number is negative or is greater than or equal to KMaxLocalDrives.

This panic is raised by the Lookup() member function of RLibrary when the ordinal number of the required DLL function, is zero or negative.

Not used.

Not used.

This panic is raised when setting a new currency symbol using the User::SetCurrencySymbol() function.

The panic occurs when the length of the descriptor containing the new symbol is greater than KMaxCurrencySymbol.

This panic is raised by the CreateDoubleEndedLocal() and CreateDoubleEndedGlobal() member functions of RChunk when the lower address of the committed region is negative.

This panic is raised by the CreateDoubleEndedLocal() and CreateDoubleEndedGlobal() member functions of RChunk when the upper address of the committed region is negative.

This panic is raised by the CreateDoubleEndedLocal() and CreateDoubleEndedGlobal() member functions of RChunk when the upper address of the committed region is lower than the lower address of the committed region.

This panic is raised by the CreateDoubleEndedLocal() and CreateDoubleEndedGlobal() member functions of RChunk when the upper address of the committed region is lower than the maximum size to which this chunk can be adjusted.

This panic is raised by RChunk::AdjustDoubleEnded() when the lower address of the committed region is negative.

This panic is raised by RChunk::AdjustDoubleEnded() when the upper address of the committed region is negative.

This panic is raised by RChunk::AdjustDoubleEnded() when the upper address of the committed region is lower than the lower address of the committed region.

This panic is raised when constructing an array of pointers, an RPointerArray, and specifying a granularity value which is one of the following:

1. zero

2. negative

3. greater than 0x10000000.

This panic is raised when constructing an array of fixed length objects, an RArray, and specifying a key offset value which is one of the following:

1. negative

2. not a multiple of 4

3. greater than or equal to the size of the array elements.

This panic is raised when constructing an array of fixed length objects, an RArray, and the length of the array elements is one of the following:

1. zero

2. negative

3. greater than 640.

This panic is raised when an index value passed to a member function of RArray or RPointerArray identifying an array element, is out of bounds.

This panic is raised when the value identifying the insertion position in a call to RArray::Insert() or RPointerArray::Insert(), is either negative or greater than the number of elements in the array.

This panic is raised when an index value passed to Mem::CollationMethodByIndex() or Mem::CollationMethodId() is out of bounds.

This panic is raised when an index value passed to TFixedArray::At() or TFixedArray::operator[] is out of bounds.

Not used.

Not used.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists when the parameter is too big.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists when an index value for the parameters is outside its permitted range.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists when an index value for the parameters is outside its permitted range.

This panic is raised in debug mode only.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

Not used.

This panic occurs in the construction of an RPointerArray object from an existing pointer array object, when the number defining the number of entries in the existing array is not positive.

This panic is raised by RChunk::Commit() when the value of the offset of the committed region is negative.

This panic is raised by RChunk::Commit() when the size of the the committed region is negative.

This panic is raised by RChunk::Allocate() when the size of the the committed region is negative.

This panic is raised by RChunk::Decommit() when the value of the offset of the committed region is negative.

This panic is raised by RChunk::Decommit() when the size of the the committed region is negative.

This panic is raised when an invalid chunk type has been passed to the internal member RChunk::Create()

This panic is raised when a global chunk is being created and no name has been specified.

This panic is raised when creating a 'normal' chunk and the offset of the bottom of the new committed region from the base of the chunk's reserved region is not zero.

This panic is raised by the internal function RLibrary::Init() when the function that constructs static data following a DLL load, leaves.

This panic is raised internally, if a call to the static data destructors following a library handle close, leaves.

This panic is raised in a call to RAllocator::Close() when the number of handles is greater than the maximum allowed, RAllocator::EMaxHandles.

This panic is raised by the internal RHeap constructor when the offset value is invalid.

This panic is raised by the Symbian internal function RHeap::Reduce() on failure.

This panic is raised by the Symbian internal function RHeap::Reset() on failure.

This panic is raised by the Symbian internal function RHeap::WalkCheckCell() on a bad free cell size.

This panic is raised by the Symbian internal function RHeap::Initialise() on a bad alignment value.

Not used.

This panic is raised when an unimplemented pure virtual function is called.

This panic is raised when a User::Leave() is called and there is no TRAP frame.

This panic is raised when a mathematical function fails with an unrecognized exception, i.e. one that is none of: KErrArgument, KErrDivideByZero, KErrOverflow or KErrUnderflow.

This panic is raised by the Symbian internal function RHeap::WalkCheckCell() on a bad cell type.

This panic is raised when descriptors convert integers into text, and an invalid radix is passed, i.e. a value that is not one of the TRadix enum values.

This panic is raised when converting and appending numbers in descriptors, and buffers are not aligned on even addresses.

This panic is raised in debug builds only.

Not used.

In a call to RNotifier::Notify(), the length of one or more of the descriptors containing the displayable text is bigger than the maximum TUint16 value.

In a call to one of the functions: TMonthName::Set() TMonthNameAbb::Set() TDayName::Set() TDayNameAbb::Set()

the month or day value is outside the permitted range of values.

This panic is raised internally by the descriptor formatting functions during the handling of the variable parameter lists.

In a call to TDes8::Expand(), either the length, or the maximum length, or the pointer to the data is not an even number.

In a call to TDes8::Collapse(), either the length, or the maximum length, or the pointer to the data is not an even number.

In a call to one of the TSecurityPolicy constructors, the specified capability was found to be inavlid.

In a call to TSecurityPolicy::CheckPolicy, the security policy was found to be corrupt.

In a call to TSecurityPolicy::TSecurityPolicy(TSecPolicyType aType), aType was not one of ETypePass or ETypeFail.

This panic is raised when constructing an RPointerArray or RArray if the specified minimum growth step is less than or equal to zero or is greater than 65535.

This panic is raised when constructing an RPointerArray or RArray if the specified exponential growth factor is less than or equal to 1 or is greater than or equal to 128.

This panic is raised if code inside an __ASSERT_*_NO_LEAVE harness leaves.

A function was used to grow a cell on the heap, but it did not grow as expected.

An attempt was made to install a Win32 SE handler not on the stack.

This panic is raised when the caller of an API doesn't have the right capabilities to call the specific API that raises this panic. Please consult the documentation for the API in question to learn what capabilities you need to call it.

This panic is raised if a NULL function pointer is passed in as the hash function when constructing a hash table class.

This panic is raised if a NULL function pointer is passed in as the identity relation when constructing a hash table class.

This panic is raised if a negative element size is specified when constructing a hash table class.

This panic is raised if, when constructing a hash table class, the specified key offset is inconsistent with the specified element size.

This panic is raised in debug builds only if a deleted entry still remains after a hash table reform. It should never occur, since it signifies an error in the hash table implementation.

This panic should never occur since it signifies an error in the hash table implementation.

This panic should never occur since it signifies an error in the hash table implementation.

This panic should never occur since it signifies an error in the hash table implementation.

This panic should never occur since it signifies an error in the hash table implementation.

This panic should never occur since it signifies an error in the hash table implementation.

This panic is raised if, while attempting to step a hash table iterator to the next entry, the iterator is found to point to an invalid table entry. This will typically occur if elements have been removed from the hash table without resetting the iterator.

This panic is raised if, while interrogating the current position of a hash table iterator, the iterator is found to point to an invalid table entry. This will typically occur if elements have been added to or removed from the hash table without resetting the iterator.

This panic is raised if an invalid argument is passed to the Reserve() function on any of the hash table classes.

The Win32 SE handler chain has been corrupted.

This panic is raised if an invalid argument is passed to the Reserve() function on the RArray<T> or RPointerArray<T> classes.