[EMAIL PROTECTED] wrote:
>
>>Records left locked in closed, unprotected database.'
>>Would someone at Palm look at the 3.3 source and explain the error message?
>
> This message has already been explained. Perhaps you could look for it in the
> archives (www.egroups.com)?
>
>>The thing is the app has >not< opened any databases.
>
> Well, your app is a database. It was opened when it was run. Perhaps a
> resource is being locked more than it's being unlocked? A simple way to check
> is to run your app 16 times. If you crash with a chunk overlocked warning,
> well, then, bingo! You're a winner!
my thanks to Roger for his reply. perhaps i should have been less polite, and a
little more direct in my initial posting.
i believe that the cause of this message lies either with a malformed "assert"
in the 3.3b1 ROM which results in this message being erroneously posted, or that
the MW Debugger is the cause of the error.
this POSEr message occurs despite the fact that my app has >not< explicitly
opened any database or resource. in an effort to determine if a database was
being implictly opened for me, i trap-patched DmOpenDatabase and
DmCloseDatabase, re-routing them so that i could see what .pdbs were being
opened for me behind the scenes. as i mentioned in my original posting, the OS
does while (a) handling my PrefGetPreferences call, and (b) in SysHandleEvent
handling 'launchChr' when i tap on the App Launcher button to switch out of my
app. In both cases the Prefs database is closed by the OS.
note that this complaint is not voiced by the 3.3b1 Debug ROM if i run my app
outside of the MW Debugger.
so perhaps the Palm and MW folkes would take a look at what's going on?
> The fastest way to figure out these problems is to use the console comands. The
> command 'opened' shows the list of opened databases. The command 'hd 1' shows
> the chunks in the storage heap. Look for a locked chunk owned by the database
> being closed.
Roger, i would love to. but the Heap commands are non-functional in R5 under NT
4.0. this is a continuing source of annoyance as those commands would be most
helpful for exactly the reasons you describe.
best regards,
steve
--
Steve Palmen
mailto: [EMAIL PROTECTED]
phone : 425.990.2510
--
The statements and opinions expressed here are my own and do not necessarily
represent those of the Oracle Corporation.