Bulent,
I had this problem last night.
Somewhere you have probably initialized a pointer to NULL, and then
written to it. Suggest you do some alerting to find the section of code
(probably one line) that is causing the problem. A favorite of mine is to
create an alert that tells me where I am in the program and then focus it
through repeated tests to the faulty code (can take some time though).
Regards, Ian Alston
----- Original Message -----
From: "Bulent Gecer" <[EMAIL PROTECTED]>
Newsgroups: palm-dev-forum
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Tuesday, September 26, 2000 7:04 PM
Subject: SysAppLaunch(...) bug?
> I have two apps, app1 and app2. In app1 I do
>
> SysAppLaunch(0,DmFindDatabase(0, "app2"), 0, sysAppLaunchCmdNormalLaunch ,
> NULL, NULL);
>
> which launches app2 successfully, but when I exit app2 either by pushing
the
> application launcher button or by doing
>
> if(eventP->data.ctlEnter.controlID ==
>
tton){
> MemSet(&newEvent, sizeof(EventType), 0);
> newEvent.eType = appStopEvent;
> EvtAddEventToQueue(&newEvent);
> handled = true;
>
> in app2, POSE complains with the following varning:
>
> " "app1" 1.0 has just written to memory location zero (NULL)"
>
> Now, is this a bug in SysAppLaunch or in POSE or have I done anything wrong to
>generate this warning?
>
> Kind regards,
>
> /Bulent Gecer
>
>
>
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe, please see
>http://www.palmos.com/dev/tech/support/forums/
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
