Hello,
I'm trying to add a feature during a sysAppLaunchCmdHandleSyncCallApp.
Below is a code snippet I used:
TestCommFeature *pTestCommGlobals = NULL;
MemPtr pReplyBuffer = NULL;
// create the globals objects, and register it
if (FtrGet(OmniCreatorId, ftrTestCommGlobals, (UInt32
*)&pTestCommGlobals)) {
pTestCommGlobals = (TestCommFeature
*)MemPtrNew(sizeof(TestCommFeature));
MemSet(pTestCommGlobals, sizeof(TestCommFeature), 0);
FtrSet(OmniCreatorId, ftrTestCommGlobals, (UInt32)pTestCommGlobals);
}
Stop Debugger here and pTestCommGlobals(addr 0x0003B310) is set to all 0's
as expected.
When the app is running under NormalLaunch code, the feature does exist but
pTestCommGlobals(addr 0x0003B310) is trashed. The instruction pointer also
jumps to some arbitrary code location, and we spin, crash, and burn. Is
this the same symptom as no A5/global access during nonNormal launch codes?
Thanks for your help,
George Aslanis
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
