If anyone can advise at to whether or not I might have a byte-boundary problem here, and how I might resolve it, I would be very appreciative.
PODS 1.2. 68k standard make. Palm OS 4 compatible calls. Data manager failure: unable to open a db. Db was literally just created in code that executed immediately before this failure. With Debug turned on, code executes perfectly (if I ever meet this Murphy character... ). With Debug turned off, crashes at this point every time. Behaviour, as described, is seen on actual Treo 650 and in Palm Emulator (yes, emulator). The emulator does not report any problems with respect to memory leaks, etc. Application is large enough that segments are necessary. I have discovered that simply moving the failing code to a different segment seems to solve the problem (both in the emulator and on the Treo 650). Again, the emulator is silent with respect to error messaging. Since the emulator is not reporting any issues, I am tempted to assume that the problem relates to byte boundaries. I've read in these forums that global structures, in particular, can cause this if sized incorrectly. But I have also read that PODS accounts for this, resizing these structures appropriately. I do have these globals in my app. Suggestions? Are there potential offenders other than the aformentioned globals? Thanks very much for any input. -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
