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.

ATDateTimeTDateTime 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(TUint32 *,TUint32 *,TInt,TUint32), Delete() and Replace() member functions of TDes16TDes16.

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(TUint32 *,TUint32 *,TInt,TUint32), 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 TDes16TDes16, when the format is S or s.

This panic is raised in debug builds only.

This panic is raised when expanding or contracting an HBufC16HBufC16 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 TDes16TDes16,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(TUint32 *,TUint32 *,TInt,TUint32), Delete() and Replace() member functions of TDes8TDes8

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(TUint32 *,TUint32 *,TInt,TUint32), 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 TDes8TDes8, when the format is S or s.

This panic is raised in debug builds only.

This panic is raised when expanding or contracting an HBufC8HBufC8 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 TDes8TDes8,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()const when the event is not a mouse/pen type event.

This panic is raised in debug builds only.

It is raised by TRawEvent::ScanCode()const 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()const 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 TKeyTKey.

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

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

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

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

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

The size specified of a new heap is smaller than the permitted minimum; it must be at least the size of a RHeapRHeap object.

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

Not used.

In a call to UserHeap::ChunkHeap(const TDesC *,TInt,TInt,TInt,TInt,TBool), 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 RHeapRHeap 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 associated 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 RHeapRHeap, 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 RHeapRHeap,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 RHeapRHeap, 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 RHeapRHeap, 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 RHeapRHeap, 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 RHeapRHeap, 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 RHeapRHeap class.

This panic is raised in debug builds only.

In a call to the Adjust() and AdjustL() member functions of an RHeapRHeap, 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 RHeapRHeap, the new size for the cell being reallocated is a negative value.

This panic is caused by the UserHeap::ChunkHeap(const TDesC *,TInt,TInt,TInt,TInt,TBool) static function when the value defining the minimum length of the heap is negative.

This panic is caused by the UserHeap::ChunkHeap(const TDesC *,TInt,TInt,TInt,TInt,TBool) 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 RHeapRHeap 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 RHeapRHeap and the heap type is not EChunkNormal.

This panic is raised by the UnGet() member function of the 8-bit variant lexical analyzer, TLex8TLex8, 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, TLex8TLex8, 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, TLex8TLex8, 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, TLex8TLex8, 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, TLex16TLex16, 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, TLex16TLex16, 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, TLex16TLex16, 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, TLex16TLex16, 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 TDateSuffixTDateSuffix 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 RSessionBaseRSessionBase, 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 TSglQueTSglQue 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(TUint32 *,TUint32 *,TInt,TUint32) member function of TSglQueTSglQue, when that object is not in the list.

Not used.

This panic is raised by the constructor of a doubly linked list header, a TDblQueTDblQue 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 TDblQueTDblQue, 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 TDblQueIterTDblQueIter; 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 TRegionTRegion.

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 TRegionTRegion, using the Sort(TUint32 *,TInt) member function of TRegionTRegion.

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(TCdtPanic) member function of RTestRTest, the test class.

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

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

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

This panic is raised by Mem::Compare(const TUint8 *,TInt,const TUint8 *,TInt), Mem::CompareC(const TUint8 *,TInt,const TUint8 *,TInt) and Mem::CompareF(const TUint8 *,TInt,const TUint8 *,TInt) 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(const TUint8 *,TInt,const TUint8 *,TInt), Mem::CompareC(const TUint8 *,TInt,const TUint8 *,TInt) and Mem::CompareF(const TUint8 *,TInt,const TUint8 *,TInt) 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(TAny *,const TAny *,TInt) 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(TAny *,const TAny *,TInt) 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(TAny *,const TAny *,TInt) 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(TAny *,const TAny *,TInt) 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(TAny *,TAny *,TInt) 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(TAny *,TInt,TChar) and Mem::FillZ(TAny *,TInt) 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.

The value for the number of records to be sorted passed to User::QuickSort(TInt,const TKey &,const TSwap &) is negative.

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

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

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

This panic is raised when a local or global chunk is created using the RChunkRChunk 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 RChunkRChunk 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 RChunkRChunk 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 RChunkRChunk.

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 RSemaphoreRSemaphore 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 RThreadRThread.

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 RThreadRThread.

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 RThreadRThread.

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 RRefRRef when the size value passed is negative.

This panic is raised by:

1. the constructor of a time representation object, a TTimeTTime, 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 TTimeTTime, if the century offset value is either negative or is greater than or equal to 100.

3. the Time::DaysInMonth(TInt,TMonth) 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 RLibraryRLibrary 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(const TDesC &) 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 RChunkRChunk when the lower address of the committed region is negative.

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

This panic is raised by the CreateDoubleEndedLocal() and CreateDoubleEndedGlobal() member functions of RChunkRChunk 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 RChunkRChunk 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(TInt,TInt)const when the lower address of the committed region is negative.

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

This panic is raised by RChunk::AdjustDoubleEnded(TInt,TInt)const 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 RPointerArrayRPointerArray, 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 RArrayRArray, 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 RArrayRArray, 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 RArrayRArray or RPointerArrayRPointerArray 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(const T &,TInt) or RPointerArray::Insert(const T *,TInt), 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(TInt) or Mem::CollationMethodId(TInt) is out of bounds.

This panic is raised when an index value passed to TFixedArray::At(TInt) 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 RPointerArrayRPointerArray 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(TInt,TInt)const when the value of the offset of the committed region is negative.

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

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

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

This panic is raised by RChunk::Decommit(TInt,TInt)const 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(TChunkCreateInfo &)

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 RHeapRHeap constructor when the offset value is invalid.

This panic is raised by the Symbian internal function RHeap::Reduce(SCell *) 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(TAny *,TCellType,TAny *,TInt) 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(TInt) 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(TAny *,TCellType,TAny *,TInt) 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(const TDesC &,const TDesC &,const TDesC &,const TDesC &,TInt &,TRequestStatus &), 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(TMonth) TMonthNameAbb::Set(TMonth) TDayName::Set(TDay) TDayNameAbb::Set(TDay)

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 TSecurityPolicyTSecurityPolicy constructors, the specified capability was found to be inavlid.

In a call to TSecurityPolicy::CheckPolicy(RProcess,const char *)const, the security policy was found to be corrupt.

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

This panic is raised when constructing an RPointerArrayRPointerArray or RArrayRArray 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 RPointerArrayRPointerArray or RArrayRArray 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.

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 RHeapRHeap 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.

This panic is raised when an invalid chunk attribute has been passed to the method RChunk::Create(TChunkCreateInfo &).

This panic is raised when a TChunkCreateInfoTChunkCreateInfo object with an invalid version number has been passed to the method RChunk::Create(TChunkCreateInfo &).

This panic is raised by the Set() member function of CAsyncCallBackCAsyncCallBack, if this active object is already active when the function is called.

This panic is raised by the Call() member function of CAsyncOneShotCAsyncOneShot, if the active object has not already been added to the active scheduler.

This panic is raised in debug builds only.

This panic is raised during construction of a dynamic buffer, a CBufFlatCBufFlat or a CBufSegCBufSeg object, when the value of the granularity passed to the constructors is negative.

This panic is raised when reading from a dynamic buffer, a CBufFlatCBufFlat or a CBufSegCBufSeg, using the Read() member function.

It is caused by attempting to read beyond the end of the buffer.

This panic is raised when writing to a dynamic buffer, a CBufFlatCBufFlat or a CBufSegCBufSeg, using the Write() member function.

It is caused by attempting to write beyond the end of the buffer.

This panic is raised when reading from a dynamic buffer, a CBufFlatCBufFlat or a CBufSegCBufSeg, using the Read() member function.

It is caused by specifying a negative length for the amount of data to be read.

This panic is raised when writing to a dynamic buffer, a CBufFlatCBufFlat or a CBufSegCBufSeg, using the Write() member function.

It is caused by specifying a negative length for the amount of data to be written.

This panic is raised when inserting data into a dynamic buffer, a CBufFlatCBufFlat or a CBufSegCBufSeg, using the InsertL() member function or when inserting an uninitialized region into the dynamic buffer using the ExpandL() member function.

It is caused by passing a negative length value to these functions.

This panic is raised when inserting data into a dynamic buffer, a CBufFlatCBufFlat or a CBufSegCBufSeg, using the InsertL() member function.

It is caused when the variant of InsertL(), which takes a pointer to TAny is passed a NULL pointer value.

This panic is raised when specifying the minimum amount of space that a flat dynamic buffer, a CBufFlatCBufFlat, should occupy using the SetReserveL() member function.

It is caused when the size value passed to the function is negative.

This panic is raised when specifying the minimum amount of space that a flat dynamic buffer, a CBufFlatCBufFlat, should occupy using the SetReserveL() member function.

It is caused when the size value passed to the function is less than the current size of the buffer.

This panic is raised by the Delete(), Ptr(), BackPtr() member functions of a flat dynamic buffer, a CBufFlatCBufFlat; the panic can also be raised by InsertL() and ExpandL().

It is caused when the position value passed to these functions is either negative or represents a position beyond the end of the current buffer.

This panic is raised by the Delete() member function of a flat dynamic buffer, a CBufFlatCBufFlat.

It is caused when the combination of position and length values passed to the function implies an attempt to delete data beyond the end of the flat buffer.

This panic is raised by the Delete(), Ptr(), BackPtr() member functions of a segmented dynamic buffer, a CBufSegCBufSeg); the panic can also be raised by InsertL() and ExpandL().

It is caused when the position value passed to these functions is either negative or represents a position beyond the end of the current buffer.

This panic is raised by the Delete() member function of a segmented dynamic buffer, a CBufSegCBufSeg.

It is caused when the combination of position and length values passed to the function implies an attempt to delete data beyond the end of the segmented buffer.

This panic is raised by the InsertL(), Delete(), Ptr() and BackPtr() member functions as implemented for segmented buffers, CBufSegCBufSeg, when the offset within a segment, where data is to be inserted or removed, is greater than the buffer granularity.

This panic is raised in debug builds only.

This panic is raised by the constructors of arrays of fixed length objects as represented, for example, by the classes CArrayFixFlatCArrayFixFlat, CArrayFixSegCArrayFixSeg, and CArrayFixFlat< TAny >CArrayFixFlat< TAny >.

It is caused when the record length is either negative or zero. The record length is either explicitly specified, as in the case of the CArrayFixFlat< TAny >CArrayFixFlat< TAny > class, or is implied by the length of the template class as in the case of the CArrayFixFlatCArrayFixFlat class.

This panic is raised by the constructors of arrays of fixed length objects as represented, for example, by the classes: CArrayFixFlatCArrayFixFlat and CArrayFixSegCArrayFixSeg.

It is caused when the granularity passed to the constructors is either negative or zero.

This panic is raised by the constructors of arrays of variable length objects as represented, for example, by the classes: CArrayVarFlatCArrayVarFlat and CArrayVarSegCArrayVarSeg.

It is caused when the granularity passed to the constructors is either negative or zero.

This panic is raised by the constructors of packed arrays as represented, for example, by the class CArrayPakFlatCArrayPakFlat.

It is caused when the granularity passed to the constructors is either negative or zero.

This panic is raised by any operation which accesses an element of an array by explicit reference to an index number, for example, the Delete(), InsertL() and At() member functions or the operator Operator[].

It is caused by specifying an index value which is either negative, or is greater than or equal to the number of objects currently within the array.

This panic is raised when deleting contiguous elements from an array of fixed length objects (derived from CArrayFixBaseCArrayFixBase) using the Delete() member function.

It is caused by specifying the number of contiguous elements as a zero or negative value.

This panic is raised when inserting contiguous elements into an array of fixed length objects (derived from CArrayFixBaseCArrayFixBase) using the InsertL() member function.

It is caused by specifying the number of contiguous elements as a zero or negative value.

This panic is raised when resizing an array of fixed length objects (derived from CArrayFixBaseCArrayFixBase) using the ResizeL() member function.

It is caused by specifying the number of contiguous elements as a zero or negative value.

This panic is raised when deleting contiguous elements from an array of variable length objects (derived from CArrayVarBaseCArrayVarBase) using the Delete() member function.

It is caused by specifying the number of contiguous elements as a zero or negative value.

This panic is raised when deleting contiguous elements from a packed array (derived from CArrayPakBaseCArrayPakBase) using the Delete() member function.

It is caused by specifying the number of contiguous elements as a zero or negative value.

This panic is raised when reserving space in flat arrays of fixed length objects, the CArrayFixFlatCArrayFixFlat,CArrayFixFlat< TAny >CArrayFixFlat< TAny > and CArrayPtrFlatCArrayPtrFlat classes, using the SetReserveL() member function.

It is caused by specifying the number of elements, for which space is to be reserved, as less than the current number of elements in the array.

This panic is raised when inserting or appending replicated elements to the arrays of fixed length objects CArrayFixFlatCArrayFixFlat and CArrayFixSegCArrayFixSeg using the InsertL() or AppendL() functions.

It is caused by specifying the number of replicas as negative or zero.

This panic is raised when deleting elements from a fixed length, variable length or packed array (derived from CArrayFixBaseCArrayFixBase, CArrayVarBaseCArrayVarBase and CArrayPakBaseCArrayPakBase) using the Delete() function.

It is caused when the specification of the position of the first element to be deleted and the number of contiguous elements to be deleted refers to elements which are outside the bounds of the array.

This panic is raised when inserting into, appending onto, expanding or extending a variable length array or a packed array (i.e. arrays derived from CArrayVarCArrayVar or CArrayPakCArrayPak) using the InsertL(), AppendL(), ExpandL() or ExtendL() functions respectively.

It is caused by specifying the length of the element as a negative value.

Not used.

Not used.

This panic is raised by the destructor of a CObjectCObject.

It is caused when an attempt is made to delete the CObjectCObject when the reference count is not zero.

This panic is raised by the Close() member function of a CObjectCObject.

It is caused when the reference count is negative.

This panic is raised by the Remove(TUint32 *,TUint32 *,TInt,TUint32) member function of an object container, a CObjectConCObjectCon.

It is caused when the CObjectCObject to be removed from the container is not contained by the container.

This panic is raised by the Remove(TUint32 *,TUint32 *,TInt,TUint32) member function of a container index, a CObjectConIxCObjectConIx.

It is caused when the object container, a CObjectConCObjectCon, to be removed from the index is not contained by the index.

This panic is raised by the Remove(TUint32 *,TUint32 *,TInt,TUint32) member function of an object index, a CObjectIxCObjectIx.

It is caused when the handle passed to the Remove(TUint32 *,TUint32 *,TInt,TUint32) function does not represent a CObjectCObject known to the object index.

This panic is raised by the At(), FindByName() and FindByFullName() member functions of an object container, a CObjectConCObjectCon.

It is caused when the unique ID as derived from the handle is not the same as the unique ID held by the object container.

This panic is raised by the At() member function of an object container, a CObjectConCObjectCon.

It is caused when the index represented by the handle is outside the permitted range. In effect, the handle is bad.

This panic is raised by the destructor of an active object, a CActiveCActive.

It is caused by an attempt to delete the active object while it still has a request outstanding.

This panic is raised by the Add() member function of an active scheduler, a CActiveSchedulerCActiveScheduler.

It is caused by an attempt to add an active object to the active scheduler when it has already been added to the active scheduler

This panic is raised by the SetActive() member function of an active object, a CActiveCActive.

It is caused by an attempt to flag the active object as active when it is already active, i.e. a request is still outstanding.

This panic is raised by the Install() member function of an active scheduler, a CActiveSchedulerCActiveScheduler.

It is caused by attempting to install this active scheduler as the current active scheduler when there is already a current active scheduler; i.e. an active scheduler has already been installed.

This panic is raised by the Start(), Stop() and Add() member functions of an active scheduler, a CActiveSchedulerCActiveScheduler.

It is caused by attempting to start or stop an active scheduler or by attempting to add an active object, a CActiveCActive, to the active scheduler.

This panic is raised by the Stop() member function of an active scheduler, a CActiveSchedulerCActiveScheduler.

Calling Stop() terminates the wait loop started by the most recent call to Start(). The panic is caused by a call to Stop() which is not matched by a corresponding call to Start().

This panic is raised by an active scheduler, a CActiveSchedulerCActiveScheduler.

It is caused by a stray signal.

This panic is raised by the Error() virtual member function of an active scheduler, a CActiveSchedulerCActiveScheduler.

This function is called when an active object’s RunL() function leaves. Applications always replace the Error() function in a class derived from CActiveSchedulerCActiveScheduler; the default behaviour provided by CActiveSchedulerCActiveScheduler raises this panic.

This panic is raised by the Add() member function of an active scheduler, a CActiveSchedulerCActiveScheduler, when a NULL pointer is passed to the function.

This panic is raised by the SetActive() and Deque() member functions of an active object, a CActiveCActive.

It is raised if the active object has not been added to the active scheduler.

This panic is raised by the SetPriority() member function of an active object, a CActiveCActive.

It is caused by an attempt to change the priority of the active object while it is active, i.e. while a request is outstanding).

This panic is raised by the At(), After() and Lock() member functions of the CTimerCTimer active object.

It is caused by an attempt to request a timer event when the CTimerCTimer active object has not been added to the active scheduler.

This panic is raised by the Start() member function of the periodic timer active object, a CPeriodicCPeriodic, when a negative time interval is passed to the function.

This panic is raised by the Start() member function of the periodic timer active object, a CPeriodicCPeriodic, when a negative delay time interval is passed to the function.

Not used.

Not used.

This panic is raised by the New() and NewL() member functions of CBitMapAllocator when a negative or zero size is passed to them.

This panic is raised by the Free(TInt aPos) member function of CBitMapAllocator when a position value is passed which is out of bounds.

This panic is raised by the IsFree(TInt aPos) member function of CBitMapAllocator when a position value is passed which is out of bounds.

This panic is raised by the AllocFromTopFrom(TInt aPos) member function of CBitMapAllocator when a position value is passed which is out of bounds.

Not used.

Not used.

This panic is raised by the AllocAt() member function of CBitMapAllocator when the implied position has already been allocated.

This panic is raised as a result of a call to the Pop() and PopAndDestroy() static member functions of the CleanupStackCleanupStack class.

The panic occurs when TRAPs have been nested and an attempt is made to pop too many items from the cleanup stack for the current nest level.

This panic is raised as a result of a call to the Pop() and PopAndDestroy() static member functions of the CleanupStackCleanupStack class.

The panic occurs when attempt is made to pop more items from the cleanup stack than are on the cleanup stack.

The panic is raised as a result of a call to the Pop() and PopAndDestroy() static member functions of the CleanupStackCleanupStack class.

The panic occurs when an attempt is made to pop more items from the cleanup stack than are on the cleanup stack.

This panic is raised if an attempt is being made to insert a cleanup item into a position on the cleanup stack reserved for marking the current TRAP nest level.

In practice this error occurs if the call to CleanupStack::PushL(TAny *) happens when there has been no call to TRAP.

This panic is raised when building a TCleanupStackItem which is to be added to the cleanup stack.

The building of the TCleanupStackItem needs a TCleanupItemTCleanupItem and this has been constructed with a NULL cleanup operation (a TCleanupOperation).

This panic is raised if there are no free slots available on the cleanup stack to insert a cleanup item.

This panic is raised if no trap handler has been installed.

In practice, this occurs if CTrapCleanup::New() has not been called before using the cleanup stack.

This panic is raised as a result of a call to the versions of the Pop() and PopAndDestroy() static member functions of the CleanupStackCleanupStack class which take an explicit count of the items to be popped.

The panic is caused by passing a negative value for the number of items to be popped.

This panic is raised when TRAPs have been nested and an attempt is made to exit from a TRAP nest level before all the cleanup items belonging to that level have been popped off the cleanup stack.

This panic is raised by the constructor of the circular buffer base class, a CCirBufBaseCCirBufBase, when the size value passed is zero or negative.

This panic is raised by a call to the SetLengthL() member function of the circular buffer base class, a CCirBufBaseCCirBufBase, by passing a length value which is zero or negative.

This panic is raised by a call to the Add() member function of a circular buffer, a CCirBufCCirBuf when the pointer to the item to be added is NULL.

This panic is raised by a call to the Add() member function of a circular buffer, a CCirBufCCirBuf when the number of items to be added is zero or negative.

This panic is raised by a call to the Remove(TUint32 *,TUint32 *,TInt,TUint32) member function of a circular buffer, a CCirBufCCirBuf when the number of items to be removed is zero or negative.

This panic is raise by CConsoleBase::Getch() when the asynchronous request that fetches the character completes with a completion code that is not KErrNone.

Not used.

This panic is raised by the Alloc() member function of CBitMapAllocator if the object is in an inconsistnt state.

This panic is raised by the AllocFrom() member function of CBitMapAllocator if the position passed into it is outside its valid range, i.e. is negative or is greater than or equal to the size.

This panic is raised by the Alloc() member function of CBitMapAllocator if the count value passed into it is not positive.

This panic is raised by the AllocAligned() member function of CBitMapAllocator if the alignment value passed into it is negative or greater than or equal to 32.

This panic is raised by the AllocAlignedBlock() member function of CBitMapAllocator if the alignment value passed into it is negative or greater than or equal to 32.

This panic is raised by the AllocAt() member function of CBitMapAllocator if the position value passed into it is outside the permitted range.

This panic is raised by the IsFree() member function of CBitMapAllocator if the position value passed into it is outside the permitted range.

This panic is raised by the Free() member function of CBitMapAllocator if the position value passed into it is outside the permitted range.

This panic is raised by the Free() member function of CBitMapAllocator if attempting to free a block that is not allocated.

This panic is raised by the Free() member function of CBitMapAllocator if attempting to allocate a block that is not free.

This panic is raised by call to the Replace() member function of CActiveSchedulerCActiveScheduler when the replacement active scheduler is the same as the existing active scheduler.

The panic is raised as a result of a call to the Pop() and PopAndDestroy() static member functions of the CleanupStackCleanupStack class.

The panic occurs when an the item to be popped is not the expected item.

This panic is raised by CActiveSchedulerWait::Start() when the CActiveSchedulerWaitCActiveSchedulerWait has already been started.

This panic is raised by CActiveSchedulerWait::AsyncStop() and CActiveSchedulerWait::CanStopNow()const when the CActiveSchedulerWaitCActiveSchedulerWait has not been started.

This panic is raised during construction of a CAsyncOneShotCAsyncOneShot if the attempt to open a handle to the current thread fails.

Not used.

This panic is raised if CPolicyServer::CustomSecurityCheckL(const RMessage2 &,TInt &,TSecurityInfo &), or CPolicyServer::CustomFailureActionL(const RMessage2 &,TInt,const TSecurityInfo &) are called.

Odds are that you forgot to implement one of these two functions in your CPolicyServerCPolicyServer derived Server.

This panic is raised in debug builds by the CPolicyServerCPolicyServer constructor if TPolicy::iRanges[0] does not have a value of 0.

This panic is raised in debug builds by the CPolicyServerCPolicyServer constructor if each element of TPolicy::iRanges is not greater than the previous.

This panic is raised in debug builds by the CPolicyServerCPolicyServer constructor unless every element in TPolicy::iElementsIndex is valid. Every element, x, must not be one of (ESpecialCaseHardLimit <= x <= ESpecialCaseLimit) in order to be valid. See CPolicyServer::TSpecialCase for more information.

This panic is raised in debug builds by the CPolicyServerCPolicyServer constructor if TPolicy::iOnConnect has an invalid value. iOnConnect must not be one of (ESpecialCaseHardLimit <= x <= ESpecialCaseLimit) in order to be valid. See CPolicyServer::TSpecialCase for more information.

This panic is raised if CPolicyServer::iPolicy is found to be invalid for an unkown reason. There is a good chance that your policy would cause the server to panic with one of the above specific policy panic codes if you run it in debug mode. See the policy server documentation for a description of a valid policy.

The value returned from CustomSecurityCheckL or CustomFailureActionL was invalid. See CPolicyServer::TCustomResult for a list of valid results.

This panic is raised in debug builds by the CPolicyServerCPolicyServer constructor if TPolicy.iRangeCount is not greater than 0. All policies given to the policy server must contain at least 1 policy.

This panic is raised by the policy server framework if a message fails a policy check (custom or not) and the associated action is EPanicClient.

This panic is raised by CObjectIxCObjectIx class methods if inconsistent data condition occurs It can appear in debug build only.