Category: +PLAT-Generic Kernel

diff -r 4816d766a08a -r f345bda72bc4 Symbian3/PDK/Source/GUID-1AA1466C-707A-5A28-8B35-E9F4BBD69ABA.dita --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Symbian3/PDK/Source/GUID-1AA1466C-707A-5A28-8B35-E9F4BBD69ABA.dita Tue Mar 30 11:56:28 2010 +0100 @@ -0,0 +1,136 @@ + + + + + +Category: +PLAT-Generic Kernel +

These panics represent errors which are detected by generic Kernel code. +They are caused by passing bad or contradictory parameters to functions.

The thread causing the panic is terminated.

+ + + + +

This panic is raised at system startup time if the secondary process +cannot be created.

+ + +

This panic is raised when a semaphore, a DPlatSemaphore, +is created and a negative count value is passed to the member function creating +it.

+ + +

This panic is raised when a semaphore, a DPlatSemaphore, +is signalled and the count value, if specified, is negative.

+ + +

This panic is raised when fetching the home address of a specified +address relative to the thread's process and the specified address is invalid.

+ + +

7.8.9

These panics are raised when an illegal attempt is made to kill +a thread, a DPlatThread; the thread may already be dead +or its status may be unknown.

+ + +

This panic is raised when an attempt is made to resume the first +thread in a process, a DPlatProcess, when that process +has not been loaded.

+ + +

This panic is raised when looking up a function by ordinal in a +library, a DPlatLibrary. The panic occurs when the specified +ordinal number is zero or negative.

+ + +

This panic is raised because of a failure in the initialization +of the Hardware Abstraction Layer (HAL); specifically, the startup reason +is not recognized.

+ + +

This panic is raised because of a failure in the initialization +of the HAL; specifically, the keyboard could not be initialized.

+ + +

This panic is raised because of a failure in the initialization +of the HAL; specifically, the x-y input device could not be initialized.

+ + +

19-21

These panics are raised by failures during system startup.

+ + +

This panic is raised when a failure occurs in dispatching an exception.

+ + +

This panic is raised when an attempt is made to create a hardware +chunk when that chunk has already been created.

+ + +

This panic is raised when a Kernel fixed heap is being created and +the specified maximum length is negative.

+ + +

This panic is raised when the Kernel attempts to mutate a fixed +heap into a chunk heap and the specified minimum length is different from +the current minimum length.

+ + +

This panic is raised in debug builds only.

This panic +is raised by the millisecond timer when a call back has already been queued.

+ + +

This panic is raised in debug builds only.

This panic +is raised during debugging when handling an exception by the Debug::HandleExceptionfunction, +and a write operation to the remote thread running the monitor program fails.

+ + +

This panic is raised when setting up the context for a newly created +thread and the specified thread type, which defines the context, is not recognized.

+ + +

This panic is raised if there is no screen-switch-on handler.

+ + +

This panic is raised if a system thread has been panicked.

+ + +

This panic is raised when an attempt is made to move a fixed address +chunk.

+ + +

93-99

These panics are raised during initialization of the MMU (Memory +Management Unit) if creation of various components fails; for example, the +domain allocator or the page table linear allocator.

+ + + +

\ No newline at end of file