From the archives on Yahoo, Wed April 11, 2001; Steve Achelis posted a
message asking for information on crash that occurred when gremlin testing.
Following call to menu event, error indicated that the program "just read
from an unallocated chunk of memory" and it occurred with the following in
the stack;
PilotMain
PemsMain
EventLoop
0x10C4C6F2( SysEventGet )
0x10C5427C( WinSetDrawWindow )
0x10C5427C( WinSetDrawWindow )
0x10C5290A( WinValidateHandle )
Was this ever resolved? I can't find any reference to a solution in the
archive and I'm running into exactly the same error. In my case it's not
just from gremlin testing.
I can add that;
I've only seen it occur on Palm OS 3.5 debug ROMs
I've never seen it occur on Palm OS 3.3 debug ROMs (my app built for
3.0 & up so didn't go lower)
it only occurs after the app has been shut down (select app
launcher), restarted (tap app icon to restart app), and then the menu item
is selected; but not every time, maybe one in three times. As long as you
keep the app running after initial load and run, you can bounce around
forever and it will never fail.
I have another application that is very similar in structure to the one
that is failing, and it never fails. It's similar enough that I can't see
an operational difference that should make one work and the other bomb. The
data is different, the forms are different but the way things are handled is
essentially the same; at least best as I can tell so far. (That's what I'm
working on now, why one and not the other. I'm down to the point where I'm
going to start changing things that shouldn't make any difference in an
attempt to find it.)
If this has been resolved, could someone point me at the solution? If
not, anyone know anything about this?
Thanks
Terry Riegle
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
