> After much interaction with a 5.0 developer (name withheld to protect
the
> innocent), we determined my application actually runs absolutely
wonderful
> on PalmSim and 5.0. As long as the Debugger isn't involved, that is.
Which
> took quite a while to figure out, because I was the only way I was
testing
> my app was while running under PalmSim and 5.0 from the debugger so I
could
> trap "surprises".
>
> So, my application that runs fine from the Debugger with POSE 3.4 (and
any
> version of Palm OS up to 4.1) has a problem with the Debugger and
> PalmSim/5.0. It appears that the Debugger is opening the .prc with
Write
> access, and leaving it that way for the duration of the debug session.
So,
> my application code listed above trips on the "DmOpenDatabase"
function.
>
> My very patient 5.0 developer contact suggested I contact MW, and in
> particular, Ben Combee, via this newsgroup to report the ... situation
??

I'll forward this on to our debugger engineer, but I don't think there
is a good fix. When we load an app onto a device for debugging, we lock
the database so it won't move and affect the mapping of memory addresses
to functions. We also have the DB open for writing, since breakpoints
are implemented by changing the object code in memory -- a breakpoint
modifies the instructions so when they're executed the debugger is
activated.



--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/tech/support/forums/