Re: Strange crash when beaming to PalmOS 3.x
1) The crash occurs even if I remove this attribute from the database and send it manually (separately from the application). 2) The crash doesn't occur on the 3.5 emulator when sending the database to itself. 3) What modified database notification? I use sysAppLaunchCmdExgReceiveData and then pretty standard stuff - ExgAccept, StrCaselessCompare, ExgReceive, ExgDisconnect, ExgDBRead, DmOpenDatabase, DmCloseDatabase, TimDateTimeToSeconds, FrmAlert, DmDeleteDatabase, DmQueryRecord, DmGetLastErr, MemHandleLock and MemHandleUnlock. Not all of them all the time, of course, but no others at any time during the database receiving. As far as I can see, none of the above requires anything newer than 3.0 (except the fancy stuff that needs 3.5 or 4.0 but I don't use any of that) - yet the crash happens under 3.5. Any other ideas? Regards, Vesselin -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
Strange crash when beaming to PalmOS 3.x
Hello folks, My application uses a PDB database. The database has the dmHdrAttrBundle attribute, so that it can be beamed together with the application. In addition, the application itself registers to receive such a database and can send the database to another copy of itself on another device. This works without problems under PalmOS 4.x and 5.x. It causes a crash on devices running PalmOS 3.x. Unfortunately, I don't have such a device myself, so I can't easily see what exactly is happening. The documentation says that the dmHdrAttrBundle attribute applies only to PalmOS 4.0 and higher. I'm not sure what applies means exactly here. OK, sure, the Launcher of PalmOS 3.x won't honor this attribute - but can it cause it to crash when receiving? In any case, even if I remove this attribute from the database, the crash still occurs. It occurs even if I try to send the database with the application. And, no, I am not using any global variables. Any idea how to find the where the problem is? I don't have a PalmOS 3.x device, so I can't debug on the device. The emulator doesn't support infrared communication, so I can't start two emulators and have the database beamed from one to the other, as I can do with the simulators. I tried using the shortcut-dot-t to beam the database from the emulator to itself - but then the crash doesn't occur. Any other ideas? Regards, Vesselin -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
Re: Strange crash when beaming to PalmOS 3.x
The bundle attribute is NOT supported on OS 3.x. If the recevier crashes, it's likely that the code in your app that handles the modified database notification is using an OS 4.x+ system trap. On 3/15/06, Dr. Vesselin Bontchev [EMAIL PROTECTED] wrote: Hello folks, My application uses a PDB database. The database has the dmHdrAttrBundle attribute, so that it can be beamed together with the application. In addition, the application itself registers to receive such a database and can send the database to another copy of itself on another device. This works without problems under PalmOS 4.x and 5.x. It causes a crash on devices running PalmOS 3.x. Unfortunately, I don't have such a device myself, so I can't easily see what exactly is happening. The documentation says that the dmHdrAttrBundle attribute applies only to PalmOS 4.0 and higher. I'm not sure what applies means exactly here. OK, sure, the Launcher of PalmOS 3.x won't honor this attribute - but can it cause it to crash when receiving? In any case, even if I remove this attribute from the database, the crash still occurs. It occurs even if I try to send the database with the application. And, no, I am not using any global variables. Any idea how to find the where the problem is? I don't have a PalmOS 3.x device, so I can't debug on the device. The emulator doesn't support infrared communication, so I can't start two emulators and have the database beamed from one to the other, as I can do with the simulators. I tried using the shortcut-dot-t to beam the database from the emulator to itself - but then the crash doesn't occur. Any other ideas? Regards, Vesselin -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
