I'm seeing a bus error in my application during a hotsync. To see it happen
in the debugger, I used a null modem cable to hotsync from within the
emulator. This is my stack after the debugger sees the exception:
0x10d141a4(SyncThreadBeginSync)
0x10c325f2(<unknown>)
0x10c32d7a(<unknown>)
0x10c3551e(<unknown>)
0x10c3755e(<unknown>)
0x10c11070(SysAppLaunch)
0x10c11ac8(PrvCallSafely)
0x254e4()
PilotMain
handleSyncCall
0x10c32b36(<unknown>)
0x10c36600(<unknown>)
0x10caaa4e(PadHtalSendReply)
0x10cabaec(PrvKeepAliveOn)
0x10d146de(PrvHtalAsyncRequestCallback)
When I step through the code line by line, the above happens when I step
over DlkControl.
My app is doing quite a bit of work before calling DlkControl. I have combed
through this code and am pretty confident that it is not corrupting
anything. So I replaced all the work with a simple "SysTaskDelay(494)". (494
was the number of ticks my work was taking.) It still crashed. Reducing the
delay, or reducing the work I do make the crash go away.
It seems like an application must respond to a SyncCallRemoteModule within a
pretty short period of time. True? Can anyone shed any light on this? I've
tried periodically calling DlkControl to try to keep the desktop link alive,
but that didn't seem to have any effect.
bill
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
