Symbian3/SDK/Source/GUID-1AA1466C-707A-5A28-8B35-E9F4BBD69ABA.dita
changeset 7 51a74ef9ed63
equal deleted inserted replaced
6:43e37759235e 7:51a74ef9ed63
       
     1 <?xml version="1.0" encoding="utf-8"?>
       
     2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
       
     3 <!-- This component and the accompanying materials are made available under the terms of the License 
       
     4 "Eclipse Public License v1.0" which accompanies this distribution, 
       
     5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
       
     6 <!-- Initial Contributors:
       
     7     Nokia Corporation - initial contribution.
       
     8 Contributors: 
       
     9 -->
       
    10 <!DOCTYPE concept
       
    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
       
    12 <concept id="GUID-1AA1466C-707A-5A28-8B35-E9F4BBD69ABA" xml:lang="en"><title>Category:
       
    13 PLAT-Generic Kernel</title><prolog><metadata><keywords/></metadata></prolog><conbody>
       
    14 <p>These panics represent errors which are detected by generic Kernel code.
       
    15 They are caused by passing bad or contradictory parameters to functions.</p>
       
    16 <p>The thread causing the panic is terminated.</p>
       
    17 <table id="GUID-368296FD-66B3-54BC-B531-6F096BEB783D">
       
    18 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/>
       
    19 <tbody>
       
    20 <row>
       
    21 <entry><p><codeph>0</codeph> </p> </entry>
       
    22 <entry><p>This panic is raised at system startup time if the secondary process
       
    23 cannot be created.</p> </entry>
       
    24 </row>
       
    25 <row>
       
    26 <entry><p><codeph>2</codeph> </p> </entry>
       
    27 <entry><p>This panic is raised when a semaphore, a <xref href="GUID-76265A73-5D41-3F85-A482-6627257154D2.dita"><apiname>DPlatSemaphore</apiname></xref>,
       
    28 is created and a negative count value is passed to the member function creating
       
    29 it.</p> </entry>
       
    30 </row>
       
    31 <row>
       
    32 <entry><p><codeph>3</codeph> </p> </entry>
       
    33 <entry><p>This panic is raised when a semaphore, a <codeph>DPlatSemaphore</codeph>,
       
    34 is signalled and the count value, if specified, is negative.</p> </entry>
       
    35 </row>
       
    36 <row>
       
    37 <entry><p><codeph>6</codeph> </p> </entry>
       
    38 <entry><p>This panic is raised when fetching the home address of a specified
       
    39 address relative to the thread's process and the specified address is invalid.</p> </entry>
       
    40 </row>
       
    41 <row>
       
    42 <entry><p><codeph>7.8.9</codeph> </p> </entry>
       
    43 <entry><p>These panics are raised when an illegal attempt is made to kill
       
    44 a thread, a <xref href="GUID-3DBB4A86-D4CE-35ED-8FF7-0811E3A05FAC.dita"><apiname>DPlatThread</apiname></xref>; the thread may already be dead
       
    45 or its status may be unknown.</p> </entry>
       
    46 </row>
       
    47 <row>
       
    48 <entry><p><codeph>12</codeph> </p> </entry>
       
    49 <entry><p> This panic is raised when an attempt is made to resume the first
       
    50 thread in a process, a <xref href="GUID-586E842E-7F35-332C-AAC4-8BE25182C3D2.dita"><apiname>DPlatProcess</apiname></xref>, when that process
       
    51 has not been loaded.</p> </entry>
       
    52 </row>
       
    53 <row>
       
    54 <entry><p><codeph>15</codeph> </p> </entry>
       
    55 <entry><p>This panic is raised when looking up a function by ordinal in a
       
    56 library, a <xref href="GUID-46530B04-82C7-3A7C-B60B-30410EFA2057.dita"><apiname>DPlatLibrary</apiname></xref>. The panic occurs when the specified
       
    57 ordinal number is zero or negative.</p> </entry>
       
    58 </row>
       
    59 <row>
       
    60 <entry><p><codeph>16</codeph> </p> </entry>
       
    61 <entry><p>This panic is raised because of a failure in the initialization
       
    62 of the Hardware Abstraction Layer (HAL); specifically, the startup reason
       
    63 is not recognized.</p> </entry>
       
    64 </row>
       
    65 <row>
       
    66 <entry><p><codeph>17</codeph> </p> </entry>
       
    67 <entry><p>This panic is raised because of a failure in the initialization
       
    68 of the HAL; specifically, the keyboard could not be initialized.</p> </entry>
       
    69 </row>
       
    70 <row>
       
    71 <entry><p><codeph>18</codeph> </p> </entry>
       
    72 <entry><p> This panic is raised because of a failure in the initialization
       
    73 of the HAL; specifically, the x-y input device could not be initialized.</p> </entry>
       
    74 </row>
       
    75 <row>
       
    76 <entry><p><codeph>19-21</codeph> </p> </entry>
       
    77 <entry><p>These panics are raised by failures during system startup.</p> </entry>
       
    78 </row>
       
    79 <row>
       
    80 <entry><p><codeph>22</codeph> </p> </entry>
       
    81 <entry><p>This panic is raised when a failure occurs in dispatching an exception.</p> </entry>
       
    82 </row>
       
    83 <row>
       
    84 <entry><p><codeph>64</codeph> </p> </entry>
       
    85 <entry><p>This panic is raised when an attempt is made to create a hardware
       
    86 chunk when that chunk has already been created.</p> </entry>
       
    87 </row>
       
    88 <row>
       
    89 <entry><p><codeph>80</codeph> </p> </entry>
       
    90 <entry><p>This panic is raised when a Kernel fixed heap is being created and
       
    91 the specified maximum length is negative.</p> </entry>
       
    92 </row>
       
    93 <row>
       
    94 <entry><p><codeph>81</codeph> </p> </entry>
       
    95 <entry><p>This panic is raised when the Kernel attempts to mutate a fixed
       
    96 heap into a chunk heap and the specified minimum length is different from
       
    97 the current minimum length.</p> </entry>
       
    98 </row>
       
    99 <row>
       
   100 <entry><p><codeph>83</codeph> </p> </entry>
       
   101 <entry><p><i>This panic is raised in debug builds only.</i> </p> <p>This panic
       
   102 is raised by the millisecond timer when a call back has already been queued.</p> </entry>
       
   103 </row>
       
   104 <row>
       
   105 <entry><p><codeph>87</codeph> </p> </entry>
       
   106 <entry><p><i>This panic is raised in debug builds only.</i> </p> <p>This panic
       
   107 is raised during debugging when handling an exception by the <xref href="GUID-2D3F457D-F575-3B52-8C70-ADF4D004B99A.dita#GUID-2D3F457D-F575-3B52-8C70-ADF4D004B99A/GUID-4B902E02-1248-34B7-8517-6232A281D343"><apiname>Debug::HandleException</apiname></xref>function,
       
   108 and a write operation to the remote thread running the monitor program fails.</p> </entry>
       
   109 </row>
       
   110 <row>
       
   111 <entry><p><codeph>88</codeph> </p> </entry>
       
   112 <entry><p>This panic is raised when setting up the context for a newly created
       
   113 thread and the specified thread type, which defines the context, is not recognized.</p> </entry>
       
   114 </row>
       
   115 <row>
       
   116 <entry><p><codeph>90</codeph> </p> </entry>
       
   117 <entry><p>This panic is raised if there is no screen-switch-on handler.</p> </entry>
       
   118 </row>
       
   119 <row>
       
   120 <entry><p><codeph>91</codeph> </p> </entry>
       
   121 <entry><p>This panic is raised if a system thread has been panicked.</p> </entry>
       
   122 </row>
       
   123 <row>
       
   124 <entry><p><codeph>92</codeph> </p> </entry>
       
   125 <entry><p>This panic is raised when an attempt is made to move a fixed address
       
   126 chunk.</p> </entry>
       
   127 </row>
       
   128 <row>
       
   129 <entry><p><codeph>93-99</codeph> </p> </entry>
       
   130 <entry><p>These panics are raised during initialization of the MMU (Memory
       
   131 Management Unit) if creation of various components fails; for example, the
       
   132 domain allocator or the page table linear allocator.</p> </entry>
       
   133 </row>
       
   134 </tbody>
       
   135 </tgroup>
       
   136 </table></conbody></concept>