Update: Trial and error. Single step through gremlin several hundred or thousand times to try and find out where gremlins is bombing. Here is what is causing my problem.
I have a table with 2 columns. The first column is a check box which can be changed by the user. The second column is text which is not editable by the user. If I have the row highlighted (the box and text is highlighted) and press a button to run another app I get this error message. I had seen similar problem in the past when a row was highlighted and the user used the hardware scroll buttons. I'll have to dig into that code and see how I fixed it back then. I think I just removed focus from all fields on the form and it solved it. Now I guess I need to trap when the form is going to close and remove focus. I think this is found because I'm using the 3.5 debug rom. If anyone has any comments or additional input please feel free to send them along. "John Crouch" <[EMAIL PROTECTED]> wrote in message news:68010@palm-dev-forum... > > I see that the newest version of the Emulator now sends appStopEvents during > the gremlin testing. I like every bit of testing they can throw at me, but > now I'm getting an error: > > ---------- > MyAppName (1.9.0) just read from memory location 0x00003452, which is in an > unallocated chunk of memory. > > An "unallocated chunk of memory" is a chunk of memory that has not been > reserved for use by the application through calling MemPtrNew or > MemHandleNew. It should not be accessed by applications under any > circumstances. Such an access usually means that an application is accessing > a chunk that used to be allocated to the application but has since been > returned with MemPtrFree or MemHandleFree. > ---------- > > I traced this back to the appStop() function in my app where it calls > FrmCloseAllForms(). It's deep within that function call where this is > happening. Gremlins successfully sends an appStopEvent several dozen times > to my app before this one particular condition happens, which is around > 26,800 gremlin taps. Stepping through CodeWarrior through the debugger when > this happens does not take me back into any of my form code when this > happens. It calls FrmCloseAllForms() and gets deep into several assembly > language functions before the error occurs. > > If anyone has any thoughts of: > > 1. What may be happening within FrmCloseAllForms() that could be causing > this problem. > 2. What is in my particular form code that I need to add or change. > 3. How to more closely diagnose this problem. > > Please let me know. Thanks! > > > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
