Error type
|
Message example
|
Bus error
|
<application> just <access-type> memory location <location>, causing a bus error. A "bus error" means that the application accessed a memory location that is not in RAM or ROM, nor corresponds to a memory-mapped hardware register.
|
Address error
|
<application> just <access-type> memory location <location>, causing an address error. An "address error" means that the application accessed a 2 or 4-byte value at an odd (i.e., not even) memory address.
|
Illegal instruction
|
<application> just executed an illegal or unknown machine language instruction. The opcode executed was <instruction>.
|
Divide by zero
|
<application> just divided an integer by zero.
|
CHK instruction
|
<application> just executed a CHK machine language instruction that failed. Invoking this instruction is not supported in Palm OS applications.
|
TRAPV instruction
|
<application> just executed a TRAPV machine language instruction that failed. Invoking this instruction is not supported in Palm OS applications.
|
Privilege violation
|
<application> just executed opcode <instruction>, a privileged machine language instruction.
A "privileged machine language instruction" is one reserved for use by the operating system. Invoking such instructions is not supported in Palm OS applications.
|
Trace
|
<application> just executed an instruction with the CPU's "trace" mode enabled. Normally, this mode is enabled by a debugger for the purpose of single-stepping through an application. However, no debugger is currently connected to handle trace mode.
|
Trap (A or F)
|
<application> just executed an illegal or unknown machine language instruction. The opcode executed was <instruction>.
|
Trap number
|
<application> just executed a "TRAP #<number>" machine language instruction. Invoking such instructions is not supported in Palm OS applications.
|
Trap #0
|
<application> just executed a "TRAP #0" machine language instruction. This instruction is often used by debuggers to set breakpoints. However, no debugger is currently connected to handle the breakpoint.
|
Trap #8
|
<application> just executed a "TRAP #8" machine language instruction. This instruction is generated when calling the DbgBreak function as a method for breaking into an external debugger. However, no debugger is currently connected.
|
Storage heap access
|
<application> just <access-type> memory location <location>, which is in the storage heap. In order to protect the integrity of the user's data, such direct access is not allowed. Instead, applications should use special Palm OS functions for this purpose.
|
Draw window error
|
<application> just <access-type> memory location <location>. This access usually indicates that the application is calling a Window Manager function without first establishing a valid DrawWindow.
|
Illegal global variable access
|
<application> just <access-type> memory location <location>. This access usually means that the application accessed a global variable after PilotMain was called with a launch code that does not support globals. The last launch code sent to the application was "<launch-code>".
|
Mac OS floating point error
|
<application> just performed a floating point operation using a calling sequence specific to the Mac OS. This indicates that the application was compiled with the incorrect Floating Point option in the development environment that created it.
|
Stack overflow error
|
<application> has overflowed the stack. The functions currently using the stack are: <stack-crawl>.
|
Unimplemented trap
|
<application> called Palm OS routine #<trap-number> (<trap-name>). This routine does not exist in this version of the Palm OS.
|
Shared library error
|
<application> called a function in a shared library using a reference number of <number>. This reference number does not correspond to any currently installed library and is invalid.
|
Corrupted dynamic heap
|
During a regular checkup, Palm OS Emulator determined that the dynamic heap chunk with header address <location> got corrupted. <corruption-type>.
|
Program counter error
|
<application> just changed the emulated program counter to <location>. This address is invalid because <reason>. The program counter was changed when <when>.
|
Low-memory access
|
<application> just <access-type> memory location <location>, which is in low memory. "Low memory" is defined as the first 256 bytes of memory. It should not be directly accessed by applications under any circumstances.
|
System variable access
|
<application> just <access-type> memory location <location>, which is in the Palm OS global variables. "Palm OS global variables" are memory locations reserved for the private use of the Palm OS. They should not be directly accessed by applications under any circumstances.
|
LCD screen buffer access
|
<application> just <access-type> memory location <location>, which is in screen memory. "Screen memory" is the area of RAM containing the pixels appearing on the LCD display. It should not be directly accessed by applications under any circumstances. Instead, they should use the Window Manager functions for altering the contents of the display.
|
Memory-mapped hardware register access
|
<application> just <access-type> memory location <location>, which is in the memory-mapped hardware registers. "Memory-mapped hardware registers" are memory locations that control the operation of your handheld device's hardware. They should not be directly accessed by applications under any circumstances.
|
ROM access
|
<application> just <access-type> memory location <location>, which is in the ROM. Such an access has no effect, and usually indicates an error in the application.
|
Memory Manager data structure access
|
<application> just <access-type> memory location <location>, which is in Memory Manager data structures. These data structures include things like the headers preceding each block in a heap, as well as the heap header itself. Such an access usually means that an application allocated a buffer (possibly with MemPtrNew) that wasn't large enough for its purpose. When the application then tries to write data to the buffer, it writes off the end of the buffer, accessing the start of the buffer following it in memory.
|
Memory Semaphore timeout
|
The Memory Manager semaphore has been held for longer than 1 minute. PalmSource recommends that applications not acquire the Memory Manager semaphore at all, but that if they do, they should not hold the semaphore any longer than that.
|
Unallocated memory access
|
<application> just <access-type> memory location <location>, which is in an unallocated chunk of memory. An "unallocated chunk of memory" is a chunk of memory that has not been reserved for use by the application through calling MemPtrNew or MemHandleNew. It should not be accessed by applications under any circumstances. Such an access usually means that an application is accessing a chunk that used to be allocated to the application but has since been returned with MemPtrFree or MemHandleFree.
|
Unlocked memory access
|
<application> just <access-type> memory location <location>, which is in an unlocked chunk of memory. An "unlocked chunk of memory" is one that has been allocated with MemHandleNew but that has not been locked with MemHandleLock. Such an access usually means that an application allocated a buffer with MemHandleNew, locked it with MemHandleLock, unlocked it with MemHandleUnlock, and then used the pointer that was returned by MemHandleLock.
|
Unused stack access
|
<application> just <access-type> memory location <location>, which is in the unused portion of the stack. The stack range is <stack-low> - <stack-high>, and the stack pointer is <stack-pointer>. The "stack" is the area of RAM used to contain function parameters and local variables. The used portion of the stack is indicated by the stack pointer. Applications may access the area of the stack above the stack pointer, but not below it.
|
Stack almost full
|
<application> is close to overflowing the stack. The functions currently using the stack are: <stack-crawl>.
|
Sizeless object use
|
Form object ID #<object-id> (left = <left>, top = <top>, right = <right>, bottom = <bottom>) from <application> has a height or width of zero. Applications should hide objects by calling FrmHideObject instead of setting their dimensions to zero. Another way to get this error message is to call FrmCopyTitle or FrmCopyLabel to change a title or label to a string larger than what was specified in the form resource. Doing this often corrupts other objects on the form.
|
Offscreen object use
|
Form object ID #<object-id> (left = <left>, top = <top>, right = <right>, bottom = <bottom>) from <application> is completely offscreen. Applications should hide objects by calling FrmHideObject instead of placing them completely offscreen. Another way to get this error message is to call FrmCopyTitle or FrmCopyLabel to change a title or label to a string larger than what was specified in the form resource. Doing this often corrupts other objects on the form.
|
Form access
|
<application> just <access-type> memory location <location>, which is in the "<field>" field of the form starting at <form>. The data at this memory location is owned by the Form Manager. Applications should not access the data directly. Instead, they should make the appropriate Form Manager calls.
|
Form object list access
|
<application> just <access-type> memory location <location>, which is in the "<field>" field of the form object list entry with index #<index>, which belongs to the form starting at <form>. The data at this memory location is owned by the Form Manager. Applications should not access the data directly. Instead, they should make the appropriate Form Manager calls.
|
Form object access
|
<application> just <access-type> memory location <location>, which is in the "<field>" field of the <type> starting at <object>, which belongs to the form starting at <form>. The data at this memory location is owned by the Form Manager. Applications should not access the data directly. Instead, they should make the appropriate Form Manager calls.
|
Window access
|
<application> just <access-type> memory location <location>, which is in the "<field>" field of the window starting at <window>. The data at this memory location is owned by the Window Manager. Applications should not access the data directly. Instead, they should make the appropriate Window Manager calls.
|
Bitmap access
|
<application> just <access-type> memory location <location>, which is in the "<field>" field of the bitmap starting at <bitmap>. The data at this memory location is owned by the Palm OS. Applications should not access the data directly. Instead, they should make the appropriate Palm OS calls.
|
Proscribed function call
|
<application> just called Palm OS routine "<function-name>". Applications should not call this function because <reason>.
|
Memory location access
|
<application> just <access-type> memory location <location>, changing it from <old-value> to <new-value>.
|
Memory location breakpoint
|
<application> just <access-type> memory location <location>, which is in the range from <watch-start> to <watch-end> specified in the Breakpoint dialog box.
|
Memory leaks
|
Found <number> memory leaks for <application>. Information concerning the leaks can be found in the log file.
|
SysFatalAlert call
|
<application> called SysFatalAlert with the message: "<message>".
|
DbgMessage call
|
<application> called DbgMessage with the message: "<message>".
|
Invalid ROM checksum
|
The ROM you've chosen has an invalid checksum.
The most common reason for an invalid checksum has been from the use of utility programs that modify the contents of the ROM without also updating its internal checksum.
PalmSource, Inc. does not support the use of this ROM. Use it with caution.
|
ROM with incorrect device emulation
|
Unable to determine an appropriate device to emulate for this ROM file.
PalmSource, Inc. does not support the use of this ROM. Use it with caution, as the operation of a ROM with an incorrect device emulation will certainly cause the ROM to crash, and may crash the Palm OS Emulator.
|
Unsupported device ROM
|
This ROM is for a device not supported by this version of the emulator.
PalmSource, Inc. does not support the use of this ROM.
|
Missing skin files
|
Palm OS Emulator needs "skin" files in order to correctly display the hardware devices it emulates. The Emulator looks for these skins in a directory called "Skins". However, that directory was not found. Previous versions of the Emulator would look for any directory starting with the word "Skins" and search that directory for skin files. With the current Emulator, the directory must be named exactly "Skins". If you don't have any skin files at all, you can download them from the Emulator download Web page:
<http://www.palmos.com/dev/tech/tools/emulator>
Follow the instructions included with that archive for installing the files.
|