e32panic.h File Reference

Not used.

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

See also: TDateTime

Not used.

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

See also: TDesC16::Ptr()

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

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.

See also: TDes16

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.

See also: TDes16

Not used.

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 panic raised by the Ptr() member function of an 8-bit descriptor if the descriptor is invalid.

See also: TDesC8::Ptr()

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

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.

See also: TDes8

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.

See also: TDes8

Not used.

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.

Not used.

It is raised by TRawEvent::ScanCode() when the event is not a key down, up or repeat 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.

See also: TKey

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

See also: KMaxCheckedUid TUidType

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

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.

See also: UserHeap

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

See also: User::Check() RAllocator::Check() KMaxTInt

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

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.

Not used.

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

See also: TLex8

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.

See also: TLex8

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.

See also: TLex8

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.

See also: TLex16

Not used.

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

See also: TDateSuffix KMaxSuffixes

Not used.

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.

See also: RServer

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.

See also: TSglQue

Not used.

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.

See also: TDblQue

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.

See also: TRegion

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 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 when the time interval passed to the After() member function of RTimer is negative.

See also: RTimer

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.

See also: Mem

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.

See also: Mem

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.

See also: Mem

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.

See also: Mem

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

See also: User

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.

See also: RChunk

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.

See also: RChunk

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.

See also: RSemaphore

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.

See also: RCriticalSection

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.

See also: RThread

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.

See also: RThread

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.

See also: TTime Time

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.

See also: TBusLocalDrive KMaxLocalDrives

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.

See also: User KMaxCurrencySymbol

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

See also: RChunk

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.

See also: RChunk

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

See also: RChunk

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.

See also: RPointerArray

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.

See also: RArray

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.

See also: RArray RPointerArray

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

See also: TFixedArray

Not used.

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.

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

See also: RPointerArray

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

See also: RChunk

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

See also: RChunk

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

See also: RChunk

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.

See also: RChunk

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

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::Reset() on failure.

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

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

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

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.

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

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

See also: TDes8

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

See also: TSecurityPolicy

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.

See also: RPointerArray RArray

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

See also: RPointerArray RArray

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

See also: TWin32SEHTrap

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 negative element size is specified when constructing a hash table class.

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 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 an invalid argument is passed to the Reserve() function on any of the hash table classes.

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 an invalid chunk attribute has been passed to the method RChunk::Create().

See also: RChunk

This panic is raised when an invalid flag is set in the aMode parameter to UserHeap::ChunkHeap().

See also: TChunkHeapCreateMode

This panic is raised when a RReadWriteLock is closed with readers/writers still pending.

See also: RReadWriteLock

This panic is raised when a RReadWriteLock is unlocked but the lock flags are inconsistent, eg read and write lock held or no lock held.

See also: RReadWriteLock

It is raised by TRawEvent::Repeats() when the event is not a key repeat event.

This panic is raised in debug builds only.

This panic is raised when a call is made to an absent ordinal in a linked library.

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

This panic is raised in debug builds only.

See also: CAsyncOneShot

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

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

See also: CBufFlat CBufSeg

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

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

See also: CBufFlat CBufSeg

This panic is raised when inserting data into a dynamic buffer, a CBufFlat or a CBufSeg, 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.

See also: CBufFlat CBufSeg

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

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

See also: CBufFlat

This panic is raised by the Delete(), Ptr(), BackPtr() member functions of a flat dynamic buffer, a CBufFlat; 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.

See also: CBufFlat

This panic is raised by the Delete(), Ptr(), BackPtr() member functions of a segmented dynamic buffer, a CBufSeg); 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.

See also: CBufSeg

This panic is raised by the InsertL(), Delete(), Ptr() and BackPtr() member functions as implemented for segmented buffers, CBufSeg, 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.

See also: CBufSeg

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

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

See also: CArrayFixFlat CArrayFixSeg

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

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

See also: CArrayPakFlat

This panic is raised when deleting contiguous elements from an array of fixed length objects (derived from CArrayFixBase) 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 resizing an array of fixed length objects (derived from CArrayFixBase) 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 a packed array (derived from CArrayPakBase) 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 or appending replicated elements to the arrays of fixed length objects CArrayFixFlat and CArrayFixSeg using the InsertL() or AppendL() functions.

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

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 CArrayVar or CArrayPak) 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.

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

It is caused when the reference count is negative.

This panic is raised by the Remove() member function of a container index, a CObjectConIx.

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

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

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 destructor of an active object, a CActive.

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

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

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 Start(), Stop() and Add() member functions of an active scheduler, a CActiveScheduler.

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

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

It is caused by a stray signal.

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

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

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 Start() member function of the periodic timer active object, a CPeriodic, when a negative time interval is passed to the function.

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 IsFree(TInt aPos) member function of CBitMapAllocator when a position value is passed which is out of bounds.

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 CleanupStack class.

The panic occurs when 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() happens when there has been no call to TRAP().

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

This panic is raised as a result of a call to the versions of the Pop() and PopAndDestroy() static member functions of the CleanupStack 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 by the constructor of the circular buffer base class, a CCirBufBase, when the size value passed is zero or negative.

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

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

Not used.

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 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 AllocAt() 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 allocate a block that is not free.

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

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

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

Not used.

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

This panic is raised in debug builds by the CPolicyServer 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 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.

This panic is raised in debug builds by the CPolicyServer 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 CObjectIx class methods if inconsistent data condition occurs It can appear in debug build only.

This panic is raised as a result of a call to CServer2::SetPinClientDescriptors() after CServer2::Start() has been invoked on a CServer2 object.