epoc32/include/e32panic.h
branchSymbian3
changeset 4 837f303aceeb
parent 2 2fe1408b6811
     1.1 --- a/epoc32/include/e32panic.h	Wed Mar 31 12:27:01 2010 +0100
     1.2 +++ b/epoc32/include/e32panic.h	Wed Mar 31 12:33:34 2010 +0100
     1.3 @@ -1,9 +1,9 @@
     1.4  // Copyright (c) 1997-2009 Nokia Corporation and/or its subsidiary(-ies).
     1.5  // All rights reserved.
     1.6  // This component and the accompanying materials are made available
     1.7 -// under the terms of the License "Symbian Foundation License v1.0" to Symbian Foundation members and "Symbian Foundation End User License Agreement v1.0" to non-members
     1.8 +// under the terms of the License "Eclipse Public License v1.0"
     1.9  // which accompanies this distribution, and is available
    1.10 -// at the URL "http://www.symbianfoundation.org/legal/licencesv10.html".
    1.11 +// at the URL "http://www.eclipse.org/legal/epl-v10.html".
    1.12  //
    1.13  // Initial Contributors:
    1.14  // Nokia Corporation - initial contribution.
    1.15 @@ -15,8 +15,6 @@
    1.16  // 
    1.17  //
    1.18  
    1.19 -
    1.20 -
    1.21  /**
    1.22   @file e32panic.h
    1.23   @publishedAll
    1.24 @@ -344,7 +342,7 @@
    1.25  	
    1.26  	/**
    1.27      It is raised by TRawEvent::ScanCode() when
    1.28 -    the event is not a key down or key up event.
    1.29 +    the event is not a key down, up or repeat event.
    1.30      
    1.31     	This panic is raised in debug builds only.
    1.32  	*/
    1.33 @@ -1987,6 +1985,75 @@
    1.34  	@see TChunkCreateInfo
    1.35  	*/
    1.36  	EChkCreateInvalidVersion = 215,
    1.37 +
    1.38 +	
    1.39 +	/**
    1.40 +	This panic is raised when an invalid flag is set in the aMode parameter
    1.41 +	to UserHeap::ChunkHeap().
    1.42 +
    1.43 +	@see TChunkHeapCreateMode
    1.44 +	*/
    1.45 +	EHeapCreateInvalidMode = 216,
    1.46 +
    1.47 +
    1.48 +	/**
    1.49 +	This panic is raised when a RReadWriteLock is created with an invalid
    1.50 +	priority.
    1.51 +
    1.52 +	@see RReadWriteLock
    1.53 +	*/
    1.54 +	EReadWriteLockInvalidPriority = 217,
    1.55 +
    1.56 +
    1.57 +	/**
    1.58 +	This panic is raised when a RReadWriteLock is closed with readers/writers
    1.59 +	still pending.
    1.60 +
    1.61 +	@see RReadWriteLock
    1.62 +	*/
    1.63 +	EReadWriteLockStillPending = 218,
    1.64 +
    1.65 +
    1.66 +	/**
    1.67 +	This panic is raised when a RReadWriteLock is requested with too many
    1.68 +	readers or pending readers/writers.
    1.69 +
    1.70 +	@see RReadWriteLock
    1.71 +	*/
    1.72 +	EReadWriteLockTooManyClients = 219,
    1.73 +
    1.74 +
    1.75 +	/**
    1.76 +	This panic is raised when a RReadWriteLock is unlocked but the lock flags
    1.77 +	are inconsistent, eg read and write lock held or no lock held.
    1.78 +
    1.79 +	@see RReadWriteLock
    1.80 +	*/
    1.81 +	EReadWriteLockBadLockState = 220,
    1.82 +
    1.83 +
    1.84 +	/**
    1.85 +	This debug-only panic is raised if the lock has been given to a reader
    1.86 +	more than a thousand times in a row, while there is a pending writer.
    1.87 +	It is intended to give a debug indication that writer starvation might be
    1.88 +	happening.
    1.89 +
    1.90 +	@see RReadWriteLock
    1.91 +	*/
    1.92 +	EReadWriteLockWriterStarvation = 221,
    1.93 +
    1.94 +	/**
    1.95 +    It is raised by TRawEvent::Repeats() when
    1.96 +    the event is not a key repeat event.
    1.97 +    
    1.98 +   	This panic is raised in debug builds only.
    1.99 +	*/
   1.100 +	ETEventNotKeyRepeatType=222,
   1.101 +
   1.102 +	/**
   1.103 +	This panic is raised when a corrupt surrogate is found in a descriptor.
   1.104 +	*/
   1.105 +	ECorruptSurrogateFound = 223,
   1.106  	};
   1.107  
   1.108  
   1.109 @@ -2980,7 +3047,22 @@
   1.110  	It can appear in debug build only.
   1.111  	*/
   1.112  	EObjInconsistent=104,
   1.113 +	
   1.114 +	/**
   1.115 +	This panic is raised as a result of a call to the Pop() and PopAndDestroy()
   1.116 +	static member functions of the CleanupStack class.
   1.117 +	
   1.118 +	The panic occurs when the cleanup operation of a popped item modifies the 
   1.119 +	cleanup stack. In such a case, the function cannot guarantee that the correct 
   1.120 +	items will be popped.
   1.121 +	*/
   1.122 +	EClnStackModified=105,
   1.123  
   1.124 +	/**
   1.125 +	This panic is raised as a result of a call to CServer2::SetPinClientDescriptors() after
   1.126 +	CServer2::Start() has been invoked on a CServer2 object.
   1.127 +	*/
   1.128 +	ECServer2InvalidSetPin = 106,
   1.129      };
   1.130  
   1.131  #endif