Marc A. Lepage wrote:
I'm working on a rather ambitious program.
When HotSyncing the application to the device, HotSync hangs during the "clean up" stage. After a reset, the program seems to run fine.
I suspect this may be due to the program running in a mode other than sysAppLaunchCmdNormalLaunch during the clean up stage. For example, accessing globals that just don't exist.
The thing is, the PilotMain function does nothing if it isn't in normal launch mode.
So I guess I should be looking for static variables, to ensure they aren't doing anything at program startup (even if not normal launch mode)?
Are there other potential causes I should be investigating?
I'm still having this problem.
The PilotMain does nothing if not in normal launch mode. So the only thing I can think of, is if something global or static was doing something during program initialization before PilotMain is called, that is causing the problem. But, shouldn't the compiler ensure that doesn't happen in modes where globals aren't available?
I don't know an awful lot about how Palm programs get bootstrapped. I only know about the general limits (e.g. 64K segments) and lack of A5 globals in other launch modes.
I'm using CodeWarrior 9.3, and I don't get any special errors at compile time.
What should I be looking into?
OK I fixed it. After posting this again, and triple checking everything again, I noticed that I didn't have PilotMain in the first segment. That was an oversight when I built this project, my other projects were correct. Moving PilotMain into the first segment where it belongs eliminated this problem.
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
