Ok, I think I may have figured this out.... on the IIIx (the one that crashes), the library is in FLASH. Who wants to bet that is the problem? A quick look at the sources... aha! Palm guys: Can you fix the bug SysLibLoad() and SysLibRemove() which incorrectly deal with ROM-based libaries? There are some comments in there where you clear the CODE resource handle, but I think the comments are not complete and/or wrong. Even for ROM-based resource chunks, you still need to UNLOCK them and RELEASE them or the error I'm getting will occur... I don't see how the database is being closed and freeing the master pointer table before you get a chance to do your own cleanup. Thanks, Alan Pinstein Synergy Solutions, Inc. http://www.synsolutions.com 1-800-210-5293 >Ok, I'm running the EXACT same prc on a real PIIIx and on POSE with the >IIIx Debug ROM. My program uses a shared library, calling SysLibLoad() on >launch and SysLibRemove() on quit. It works perfectly, returning no error >on either device. BUT, on the real device, the 15th time I run the app it >crashes with a chunk overlocked in SysLibLoad(). Makes perfect sense. But >why the heck isn't SysLibRemove() unlocking the code resource chunk? I have >looked at the sources and don't see anything too fishy, unless the Shared >Lib table is getting corrupted somehow. > >I'd appreciate any hints. BTW - the program is Launch 'Em. This error is >occuring in a bug-fox release that I am compiling with CW MAc R/5. This >part of the code was not changed. I have tested on a PV and it doesn't >crash, either. > >I am lost on this one. > >Thanks, > >Alan Pinstein >Synergy Solutions, Inc. >http://www.synsolutions.com >1-800-210-5293
