Blackberry jvm error code & their description Part 1

Posted by Admin | Labels:
Description
The following table lists errors that can occur in the Java virtual machine (JVM) on BlackBerry devices. Contact Research In Motion® (RIM®) if you encounter any error codes not listed in this table.


Value Error Description

101Previous startup failed
The device was reset during the JVM boot process. The JVM found the boot in progress flag was set on startup. The screen is intended to break continuous reset loops so that corrective action can be taken.

102Invalid code in filesystem
The system checked the COD files in the device for modification and determined that a problem exists with one or more COD files.

If all loads fail, a build process error might occur (a problem exists with signing the COD files).

If a user action on the device resulted in this problem, the reset cycle is continuous because the code in the filesystem has been corrupted. The only recovery method is to wipe the device and restore a new system.

103 Cannot find starting address
The starting address for the boot COD file cannot be found. This might indicate that a boot COD file has not been installed on the device or that its format is invalid or corrupt.

104
Uncaught:

An uncaught Java exception was thrown by the Java code and diagnosed by the JVM. Execution can continue, or the device can be attached to a debugger on a desktop computer. The Microsoft® Windows® Event Viewer log should contain the traceback of the thrown exception.

105
Example, DbRecSize( %d ) -> %d

The file system application programming interface (API) has returned an error status for a specific operation. This might indicate a corrupt filesystem or an error in the JVM.

106
Graphics system error
An error was detected in the graphics system on the device.

107
operator new() called

A C++ class in the JVM was coded incorrectly to inherit from VMRamObject that has the correct override for operator new. Extract the current (post-reset) BUGDISP.

108
operator delete() called

A C++ class in the JVM has was coded incorrectly to inherit from VMRamObject that has the correct override for operator delete. Extract the current (post-reset) BUGDISP.


0 comments:

Your Ad Here
free counters