Enum TBasePanic

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

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.

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

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.

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

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

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

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

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

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

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

This panic is raised by the constructors of arrays of fixed length objects as represented, for example, by the classes CArrayFixFlat, CArrayFixSeg, and 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> class, or is implied by the length of the template class as in the case of the CArrayFixFlat class.

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.

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

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

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 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 inserting contiguous elements into an array of fixed length objects (derived from CArrayFixBase) 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 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 an array of variable length objects (derived from CArrayVarBase) 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 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 reserving space in flat arrays of fixed length objects, the CArrayFixFlat,CArrayFixFlat<TAny> and CArrayPtrFlat 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 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 deleting elements from a fixed length, variable length or packed array (derived from CArrayFixBase, CArrayVarBase and CArrayPakBase) 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 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.

Not used.

This panic is raised by the destructor of a CObject.

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

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 an object container, a CObjectCon.

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

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 Remove() member function of an object index, a CObjectIx.

It is caused when the handle passed to the Remove() function does not represent a CObject known to the object 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 At() member function of an object container, a CObjectCon.

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

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 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 Install() member function of an active scheduler, a CActiveScheduler.

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 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 the Stop() member function of an active scheduler, a CActiveScheduler.

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

It is caused by a stray signal.

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

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

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 SetActive() and Deque() member functions of an active object, a CActive.

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 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 At(), After() and Lock() member functions of the CTimer active object.

It is caused by an attempt to request a timer event when the CTimer 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 CPeriodic, 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 CPeriodic, 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 CleanupStack 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 CleanupStack 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 CleanupStack 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() 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 TCleanupItem 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 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 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 CCirBufBase, 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 CCirBufBase, 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 CCirBuf 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 CCirBuf when the number of items to be added is zero or negative.

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.

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 CActiveScheduler 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 CleanupStack 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 CActiveSchedulerWait has already been started.

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

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

Not used.

This panic is raised if CPolicyServer::CustomSecurityCheckL(), or CPolicyServer::CustomFailureActionL() are called.

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

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 if each element of TPolicy::iRanges is not greater than the previous.

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