Symbian Developer Library

SYMBIAN OS V6.1 EDITION FOR C++

[Index] [Glossary] [Previous] [Next]



Category: KERN-SVR

These panics represent program errors which are detected by the Kernel Server. Typically, they are caused by passing bad or contradictory parameters to functions.

The thread causing the panic is terminated.

0

This panic is raised by the Kernel Server when it attempts to close a Kernel object in response to an RHandleBase::Close() request. The panic occurs when the object represented by the handle cannot be found. The panic is also raised by the Kernel Server when it cannot find an object in the object index for the current process or current thread using the specified object index number (the raw handle number). The most likely cause is a corrupt handle.

1

This panic is raised as a result of trying to kill, terminate or panic a thread or a process. The panic occurs when:

  • the process, which is the target of the kill, terminate or panic operation, is protected and is not the same as the process invoking the operation.

  • the thread, which is the target of the kill, terminate or panic operation, is protected and is not the same as the thread invoking the operation.

The thread or process attempting the kill, terminate or panic operation is panicked.

2

This panic is raised by the Kernel Server when accessing a named CObject and the name is invalid. The name of a CObject is invalid if it contains any * ? or : characters. Specific causes are:

  • a result of a call to User::FreeLogicalDevice(), freeing a logical device driver DLL; the specified name of the device is invalid.

  • a result of a call to User::FreePhysicalDevice(), freeing a physical device driver DLL; the specified name of the device is invalid.

  • Opening a named object, for example, a named chunk, device, mutex, process or semaphore.

11

This panic is raised by the Kernel Server as a result of attempting to create a channel on a device by calling the CreateChannel() member function of the RLogicalChannel abstract class. The panic occurs when the logical device has a bad unit number.

17

This panic is raised in debug builds only.

This panic is raised by the Kernel Server if the Kernel heap fails a heap check.