From: "Claire" <[EMAIL PROTECTED]> > Specifically, the PC is forming a Palm Bitmap (V1) and sending it to the > Palm. The Palm reads off the header and displays the bitmap. The code > works fine when running on actual devices and the Palm 5.0 Release > simulator (all the header data is correct). When I try to run it on the > emulator (with any rom) or the Palm 5.0 Debug simulator, however, then > the data in the header is incorrect. > My guess would be that some of the memory or variables you're using aren't being initialised properly or possibly used after being freed. This sort of memory bug will often produce running code when the memory happens to start as zeros but then produce bugs when some change in the environment results in that memory containing old data.
>From memory the emulator has more memory protection measures in place such as writing 0xEFEF to freed memory (yes?). The debug build of the simulator might have similar protection, leading to the program working in release environments but not in the stricter debug environments. The problem, of course, is that this could be very difficult to trace. The problem is often real, but whether it will cause a problem in a real device in the future is pretty much random. You could start by making sure that all memory you use is initialised properly and taking a good look at the data corruption to see if you can identify the source. Chris Tutty -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
