I have a quick & dirty database conversion/repair program that ships with my
"real" product. It is used to upgrade the handheld databases, or to fix
linkage problems caused by older versions (i.e. very rarely).
In testing, it is occasionally getting the "UIAppShell... rec
"JB Parrett" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> A soft reset will fix this, but I know you would never depend on this to
fix an error in code.
Oh, um, yeah, that's right...
It turns out the problem was caused by not calling
MemHandleUnlock/DmReleaseResource in one part
Luc Le Blanc wrote:
Logan wrote:
But, if you are working with an appinfo block, then I think you
can be pretty confident that the LocalID is a handle and not a
pointer, so you should be safe doing the MemPtrUnlock().
Is there some release I have to do then after I unlock the pointer
I got f
What about any calls to DmNewRecord(). Do you release after those? Bob.
To summarize:
I call MemHandleUnlock for every record I call DmGetRecord or
DmQueryRecord on. I also call DmReleaseRecord when I call DmGetRecord.
I do a MemPtrUnlock on pointers I locked through MemLocalIDToLockedPt
I wrote earlier:
Another Gremlin error I keep getting is "Records left locked in closed
unprotected DB". Yet, I DmRelease every record that I DmGet,
and unlock every locked record handle. Could this come from the AppInfo
block instead of a record? I update it upon closing the app, b
worth a shot
looking into DmGetRecord.
--
Tim Kostka
http://www.nuprograms.com
"Luc Le Blanc" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> At this point, by far the most current error I get in POSE either
> testing or running the Gremlins is "Records
> > At this point, by far the most current error I get in POSE either
> > testing or running the Gremlins is "Records left locked" or "Records
> > left busy" in closed unprotected DB.
> >
> > As I don't use DmGetRecord at all (preferring DmQueryR
I get in POSE either
> testing or running the Gremlins is "Records left locked" or "Records
> left busy" in closed unprotected DB.
>
> As I don't use DmGetRecord at all (preferring DmQueryRecord, even when I
> call DmWrite later), how can I en up leavin
David Jones a écrit :
> On May 19, 2004 02:58 pm, you wrote:
> > At this point, by far the most current error I get in POSE either
> > testing or running the Gremlins is "Records left locked" or "Records
> > left busy" in closed unprotected DB.
imilar problems in Palm OS 4.0
Limited Sources. (Available at PalmOne.)
- Original Message -
From: "Luc Le Blanc" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Wednesday, May 19, 2004 8:58 PM
Subject: Records left locked or busy i
On May 19, 2004 02:58 pm, you wrote:
> At this point, by far the most current error I get in POSE either
> testing or running the Gremlins is "Records left locked" or "Records
> left busy" in closed unprotected DB.
>
> As I don't use DmGetRecord at all (pref
At this point, by far the most current error I get in POSE either
testing or running the Gremlins is "Records left locked" or "Records
left busy" in closed unprotected DB.
As I don't use DmGetRecord at all (preferring DmQueryRecord, even when I
call DmWrite later), how ca
"Wojtek" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi.
>
> My app runs fine - till HotSync.
> Every launch after HotSync gives "Records left locked in closed
unprotected
> DB" when I call DmCloseDatabase.
> I tried to check all reco
Wojtek wrote :
> My app runs fine - till HotSync.
> Every launch after HotSync gives "Records left locked in closed unprotected
> DB" when I call DmCloseDatabase.
> I tried to check all records in this DB for dmRecAttrBusy just before
> closing - all records are clear (
On Fri, 26 Mar 2004 10:00:46 +0100, Wojtek wrote:
> Hi.
>
> My app runs fine - till HotSync.
> Every launch after HotSync gives "Records left locked in closed
> unprotected DB" when I call DmCloseDatabase.
> I tried to check all records in this DB for dmRecAttrBusy
On Fri, Mar 26, 2004 at 10:00:46AM +0100, Wojtek wrote:
>
> Every launch after HotSync gives "Records left locked in closed unprotected
> DB" when I call DmCloseDatabase.
> I tried to check all records in this DB for dmRecAttrBusy just before
> closing - all records a
"Wojtek" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi.
>
> My app runs fine - till HotSync.
> Every launch after HotSync gives "Records left locked in closed
unprotected
> DB" when I call DmCloseDatabase.
> I tried to check all reco
Hi.
My app runs fine - till HotSync.
Every launch after HotSync gives "Records left locked in closed unprotected
DB" when I call DmCloseDatabase.
I tried to check all records in this DB for dmRecAttrBusy just before
closing - all records are clear (don't have this attribute set)
The PDB is 98 records long with each record being ~1Kb. The exception is
thrown towards the end of the read at the 95th or 96th record (but varies).
The exception is consistently thrown from within the call to "new" at the
last line listed below.
If new is throwing an exception, the only likely c
I know it is besides the point, but do you really programmed it all in
Assembly???
:)
Sebas
-Mensaje original-
De: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] nombre de Richard
Coutts
Enviado el: lunes, 23 de junio de 2003 22:21
Para: Palm Developer Forum
Asunto: "Records left lock
I got a report that a user couldn't open a PDB with my app with his m515.
Checking into it, it opens fine with most ROMs but when I tried to open it
with POSE running "platform41_m505_Dbg_enUS" I threw an exception with the
error
"DataMgr.c Line: 8638, Records l
On Thu, Nov 28, 2002 at 06:44:54PM -0500, Dominique wrote:
>> Of course, if I ignore this then after 15 tries I get an error when I launch
>> the app, saying that I have overlocked a record. Using the debugger (gdb) I
>> verified that I get this error BEFORE PilotMain executes, and therefore I
>> h
At 18:44 2002-11-28 -0500, you wrote:
This turned out (as is so often the case) to be my own error. I was using
C++ and was locking a font resource in the constructor. I had forgotten that
I had this object hanging around! Thanks, once again, for all the input.
However, I am interested to know
>
> Is there a special way that I must close my app when it is multisegmented.
> With an OS4.1 debug rom on POSE, I get the error:
>
> "Records left locked in closed unprotected DB"
>
> Of course, if I ignore this then after 15 tries I get an error when I
launch
>
I'm using PRC-tools 2.2. I have installed the changes from Ton van Overbeek
for multisegment GDB
Dominique
"Aaron Ardiri" <[EMAIL PROTECTED]> wrote in message
news:102817@palm-dev-forum...
> what development environment are you using?
>
> i had a fix for prc-tools 2.0 available where you comp
Thanks for these responses! John, if you wouldn't mind emailing me that
database browser, I'd appreciate it. I will investigate with more code of my
own too.
I tried using GDB to test _GccReleaseCode, and it appeared to work OK, but I
haven't checked the error codes on the unlock/release code - I'
Incidentally, assuming (and to be sure this is a big assumption :-))
that PalmOS_Startup.c (e.g. as reflected in the 5.0 SDK) really is the
startup code used by CodeWarrior, the CW runtime library uses
DmGet1Resource() in the same way and would be similarly subverted.
Nope... current versions o
On Tue, Nov 26, 2002 at 06:19:33PM -0600, Ben Combee wrote:
> This looks like a problem with the runtime library code -- the runtime
> loads all of your additional segments before PilotMain is called, and
> should unlock and release them when your app is completed. With the CW
> libraries, this
> Is there a special way that I must close my app when it is multisegmented.
> With an OS4.1 debug rom on POSE, I get the error:
>
> "Records left locked in closed unprotected DB"
>
> Of course, if I ignore this then after 15 tries I get an error when I
launch
&
I realize that my app is a database ;-)
This is, in fact, why I feel (as you do) that the runtime code is not
freeing up the necessary resources. Would it be safe for me to iterate
through all of the prc records (except the 'active' one) and unlock them?
Dominique
> Your application is a dat
At 19:26 2002-11-26 -0500, you wrote:
I should have added that if I use the POSE script to list the open
Databases, none of my apps databases have been opened.
I have 2 handles which are used to get Font pointers. I make sure that these
are unlocked and I call DmReleaseResource() on each before e
This seems to be the case. Although it is not a gdb issue - it happens even
when I don't use gdb.
Dominique
"Ben Combee" <[EMAIL PROTECTED]> wrote in message
news:102780@palm-dev-forum...
>
> At 19:14 2002-11-26 -0500, you wrote:
> >DmGetDatabaseLockState is the function to use when you have
Records left busy ." then make
> sure to use DmReleaseRecord to free it.
>
> Max
>
> Dominique wrote:
>
> > Hi,
> >
> > Is there a special way that I must close my app when it is
multisegmented.
> > With an OS4.1 debug rom on POSE, I get the error:
> >
>
At 19:14 2002-11-26 -0500, you wrote:
DmGetDatabaseLockState is the function to use when you have things like
that. Call it before closing the databse and call it at places where
you suspect that could cause the problem.
It is probably not related to the multiseg. Try make sure you have Lock
.
Sometimes if you get something like "Records left busy ." then make
sure to use DmReleaseRecord to free it.
Max
Dominique wrote:
Hi,
Is there a special way that I must close my app when it is multisegmented.
With an OS4.1 debug rom on POSE, I get the error:
"Records left l
Hi,
Is there a special way that I must close my app when it is multisegmented.
With an OS4.1 debug rom on POSE, I get the error:
"Records left locked in closed unprotected DB"
Of course, if I ignore this then after 15 tries I get an error when I launch
the app, saying that I have ov
> Actually I am now getting the error later on with the Gremlins.
The "records left locked" error?
> recPtr = (Char *) MemHandleLock(recHandle);
> err = DmWrite(recPtr, recSize, buffer, bytesReceived);
> MemHandleUnlock(recHandle);
This is a well-matched pair of lock a
amp; numBytes > 0);
if (recHandle) { //
<-- possible
problem?
DmReleaseRecord(db, index, true);
}
if (err != errNone && allocatedRecord)
DmRemoveRecord(db, index);
*indexPtr = index;
return err;
}
Danny Epstein wrote:
> > I get this err
Thanks for the quick response. There was one point where I had a continue statement.
I was under the impression that the
FrmCloseAllForms magically fixed any locked handles, etc.
Ed
Danny Epstein wrote:
> > I get this error, "Records left locked in closed unprotected database.
&g
> I get this error, "Records left locked in closed unprotected database.
> " in POSE with my app.
This indicates that you closed a database without unlocking all the record
or resources that you locked. Note that it can be resources or records,
despite the error m
I get this error, "Records left locked in closed unprotected database.
" in POSE with my app.
Here is the code snippet from my AppStop function:
FrmCloseAllForms();
/* Close the databases. */
if (gSRCatDB != 0)
error = DmCloseDatabase(gSRCatDB);
if (gSRW
Its a 4.0.1. I think your suggestion is exactly the point: When I made a "PilotMain
only" app without any ressources attached the same thing happened.
Ben Combee schrieb:
> In article <87017@palm-dev-forum>, [EMAIL PROTECTED] says...
> >
> > I've got the same! And only when the CW Debugger runs.
s. Could this have to do with wrong implementation
> of ressource databases at programming time?
>
> Werner Poschenrieder schrieb:
>
> > There is a mysterious "records left locked in closed unprotected DB2
> > when I run my app in a session with the CW debugger on a 3.5
It even occurs when I put "return errNone;" immediately at the entry of
PilotMain.
I am using some ressources. Could this have to do with wrong implementation
of ressource databases at programming time?
Werner Poschenrieder schrieb:
> There is a mysterious "records lef
In article <87017@palm-dev-forum>, [EMAIL PROTECTED] says...
>
> I've got the same! And only when the CW Debugger runs. Did you find the answer
> meanwhile? Thank you,
> Cheers Werner
>
>
> Ayers Family Member schrieb:
>
> > I created a new emulation session without any databases. I start the
There is a mysterious "records left locked in closed unprotected DB2
when I run my app in a session with the CW debugger on a 3.5 debug rom.
The first one occurs, when the debugger has not even stopped at the
initial breakpoint of pilot main (huh?)
The second occurs, when the program stop
>UIAppShell (unknown version) called SysFatalAlert with "DataMgr.c,
> > >Line: 8236, Records left locked in closed unprotected DB."
> > >
> > >So, I commented out the creation of all of my databases, and I made sure
> > >there were no records left
--- palm wrote:
>
> I'm debugging my app with POSE.
> Upon closing my app i get the message: "Records left locked in closed
> unprotected DB".
> I'm not opening any database.
> What does this message mean? Can i ignore it?
>
Normally, it means that you
Hi
I'm debugging my app with POSE.
Upon closing my app i get the message: "Records left locked in closed
unprotected DB".
I'm not opening any database.
What does this message mean? Can i ignore it?
Alex
--
For information on using the Palm Developer Forums, or to uns
> I created a new emulation session without any databases. I start the
> debugger in CodeWarrior, then I tap the Home icon to leave
> the app. The
> error still occurs even though I did not create a single
> database. How is
> this possible? How do I determine which database is open if I
> do n
AIL PROTECTED]> wrote in message
news:55669@palm-dev-forum...
>
> >UIAppShell (unknown version) called SysFatalAlert with "DataMgr.c,
> >Line: 8236, Records left locked in closed unprotected DB."
> >
> >So, I commented out the creation of all of my databases, and I
>UIAppShell (unknown version) called SysFatalAlert with "DataMgr.c,
>Line: 8236, Records left locked in closed unprotected DB."
>
>So, I commented out the creation of all of my databases, and I made sure
>there were no records left. However, the error continues to occur
The error message reads as follows:
UIAppShell (unknown version) called SysFatalAlert with "DataMgr.c,
Line: 8236, Records left locked in closed unprotected DB."
So, I commented out the creation of all of my databases, and I made sure
there were no records left. However, the error co
rch 21, 2001 3:10 PM
Subject: Re: Records left locked in closed unprotected DB
> Hi,
>
> > I have also seen this problem if you are Debugging the application from
> > CodeWarrior and you exit it in POSE. That will generate this error message
> > as well on the debu
Hi,
> I have also seen this problem if you are Debugging the application from
> CodeWarrior and you exit it in POSE. That will generate this error message
> as well on the debug ROMs.
You mean I'm not supposed to try exiting the application while the debugger
is on?
Regards,
Gee.
--
For inf
://HandAble.com
- Original Message -
From: "Bozidar Benc" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Wednesday, March 21, 2001 6:13 AM
Subject: RE: Records left locked in closed unprotected DB
> Do you have FrmCloseAllForms() i
Chris,
The FrmCloseAllForms thing was that the debug ROM would tell you there
was a possible memory leak if you didn't include that call in AppStop.
It wouldn't affect "Records left locked..." However, I do remember
there being a certain version of the emulator or debug R
> Good point (rustle, rustle). Yes. But even if I didn't why
> would this cause the 'records left locked' message?
There was a thread about that error last year, and, if I remember correctly,
someone from Palm mentioned that the OS 3.5 debug ROM will complain if
an applica
> > Do you have FrmCloseAllForms() in the AppStop function?
> Good point (rustle, rustle). Yes. But even if I didn't why
> would this cause the 'records left locked' message? I
> could understand it if the form had fields which used
> database records but it&#
"Bozidar Benc" <[EMAIL PROTECTED]> wrote
>
> Do you have FrmCloseAllForms() in the AppStop function?
>
Good point (rustle, rustle). Yes. But even if I didn't why
would this cause the 'records left locked' message? I
could understand it if the form ha
Do you have FrmCloseAllForms() in the AppStop function?
Bozidar
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Chris
> Tutty
> Sent: Wednesday, March 21, 2001 12:31 PM
> To: Palm Developer Forum
> Subject: Re: Records
"Ng Wei Gee" <[EMAIL PROTECTED]> wrote
>
> Oops, apparantly I'm wrong. The problem IS still present. However, I've
> checked to make sure that I have all the corresponding pairs of
> MemHandleLock and MemHandleUnlock/MemPtrUnlock. What
> else can I possibly check for?
>
I've seen this arise when I
Oops, apparantly I'm wrong. The problem IS still present. However, I've
checked to make sure that I have all the corresponding pairs of
MemHandleLock and MemHandleUnlock/MemPtrUnlock. What else can I possibly
check for?
Regards,
Gee.
"Ng Wei Gee" <[EMAIL PROTECTED]> wrote in message
news:42723@p
It's really weird, I made some changing to some serial port code and the
problem went away, and none of the lines "played" with the memory at all.
Regards,
Gee.
Alan Ingleby <[EMAIL PROTECTED]> wrote in message
news:42690@palm-dev-forum...
>
> Somewhere in your code, you're calling a MemHandleLo
:42501@palm-dev-forum...
>
> Hi,
>
> I've a program that creates a database open startup if it doesn't find a
> database. The funny thing is that when I quit the program while running
the
> debugger, I get the error "Records left locked in closed unprotected DB".
&
Hi,
I've a program that creates a database open startup if it doesn't find a
database. The funny thing is that when I quit the program while running the
debugger, I get the error "Records left locked in closed unprotected DB".
FWIW, this means that I've locked a record
Ah.. I was thinking of the error that went, "UIAppShell .. records left unlocked in
closed unprotected DB". There are listings about that in the archive.
-Jason
>>> [EMAIL PROTECTED] 09/03/00 11:38AM >>>
>In testing, it is occasionally getting the "UIAppShe
I thought I saw a post in the archives saying that certain ROMs mistakingly reported
this as an error. I could be mistaking this for another issue.
-Jason
>>> [EMAIL PROTECTED] 09/05/00 02:03PM >>>
On Tue, 5 Sep 2000, Jason Partyka wrote:
> There are postings about this error in the archive. Th
On Tue, 5 Sep 2000, Jason Partyka wrote:
> There are postings about this error in the archive. This error may or may not be an
>emulator isue. I recommend checking the archives for your answer.
>
> -Jason
It's not an emulator issue. The emulator does not deal with such things.
It's a problem w
There are postings about this error in the archive. This error may or may not be an
emulator isue. I recommend checking the archives for your answer.
-Jason
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
"JB Parrett" <[EMAIL PROTECTED]> wrote in message
news:23146@palm-dev-forum...
> A soft reset will fix this, but I know you would never depend on this to
fix an error in code.
Oh, um, yeah, that's right...
It turns out the problem was caused by not calling
MemHandleUnlock/DmReleaseResource in o
arely).
>
> In testing, it is occasionally getting the "UIAppShell... records left
> locked in closed unprotected DB" depending upon the particular sample
> database getting upgraded.
>
> Can anyone tell me what the impact of this might be? (I'm very short of
> t
>In testing, it is occasionally getting the "UIAppShell... records left
>locked in closed unprotected DB"
>
>Can anyone tell me what the impact of this might be?
If a record can get locked more than once and not unlocked, you could
conceivably hit the upper lock limit (
I have a quick & dirty database conversion/repair program that ships with my
"real" product. It is used to upgrade the handheld databases, or to fix
linkage problems caused by older versions (i.e. very rarely).
In testing, it is occasionally getting the "UIAppShell... rec
; (unknown version) reports "DataMgr.c, Line: 8236,Records left
> >locked in closed unprotected DB".
>
>See http://www.palm.com/devzone/docs/palmos35issues.html for three
>different reasons that this message could appear. (Plus other information
>you're likely
75 matches
Mail list logo
