Hi there,
I'm currently on the bug crunching path on our Zap!2000 game, and we've long
had a problem with the system Find button. If you go ahead and do a find,
then Cancel and return to the game then you get a 'attempt to read
unallocated memory' error from POSEr and things go quickly downhill.
Zap!2000 is a multi-segment app, and with a combination of the Palm Reporter
(ooh, such a wonderful tool!) and the debugger (not managed to get debug
information into the debugger, which makes things interesting) I've found
that the problem is with the jump tables that Multilink sets up. When
Zap!2000 regains control after a find (it's set up to ignore the PilotMain
calls that Find causes) the jump table's memory has become unallocated.
Previous to doing the call there is 32 bytes allocated for the jump table,
made slightly strange by the fact that it's owned by #0 (the OS, I presume)
and has a lock count of 15.
Has anyone come across this problem? I've been trying to disable Find during
the game but I can't fool POSEr every time... :oP
Seeya,
David
---
David Oakley - [EMAIL PROTECTED]
director, Astraware Ltd. - http://www.astraware.com/
Games for Palm: http://www.astraware.com/palm/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
